similar to: [PATCH] ia64 dump_execution_state() stub, build fix

Looks like cset 8863 included a header in xenbus.h that makes the ia64 build unhappy. domid_t isn''t define so we blow up including grant_table.h. Fix below. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 3ed537add538 linux-2.6-xen-sparse/include/xen/xenbus.h --- a/linux-2.6-xen-sparse/include/xen/xenbus.h Fri Feb 17 21:26:49 2006 +0100 +++

Keir, The patch below is necessary to get ia64 building on current xen-unstable.hg. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 3983e4f1b054 xen/arch/ia64/Rules.mk --- a/xen/arch/ia64/Rules.mk Sun Mar 12 10:03:33 2006 +0100 +++ b/xen/arch/ia64/Rules.mk Mon Mar 13 09:36:01 2006 -0700 @@ -12,7 +12,7 @@ CPPFLAGS += -I$(BASEDIR)/include -I$(BA

>From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] >Sent: 2006年5月22日 17:51 >To: Keir Fraser > >>> We just need to reverse the whole change for ia64, since both >domU >>> and domVTI are insert a hole by this auto-balloon patch. Due to >>> missing balloon support on xen/ia64 as you said, both domU and >domVTI >>> failed due to this change.

FYI, I see the following build error with this patch... MRJ ---- new warnings/errors for xen ---- keyhandler.c: In function `__dump_execstate'': keyhandler.c:96: warning: asm operand 1 probably doesn''t match constraints gmake[5]: *** [keyhandler.o] Error 1 gmake[4]: *** [/tank/ws/xvm-3.4.3/xen.hg/xen/common/built_in.o] Error 2 gmake[3]: *** [/tank/ws/xvm-3.4.3/xen.hg/xen/xen]

================== STATUS ================== I do the heavy load test of create/destroy. CREDIT scheduler(cshed_schedule) checks BUG_ON(!vcpu_running) at the end of code. It makes error. The reason is that atomic_inc(&v->pausecnt)@vcpu_pause() is called without lock. (spin_lock(&schedule_data[cpu].schedule_lock)) This lock-less "pausecnt" makes vcpu_running state changing

Hi Keir, With the recent per cpu changes, scheduler_init() now starts poking at per cpu space before we''ve configured it on ia64. This re-orders the setup calls to avoid this problem. Please apply. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 1f05ac8abda6 xen/arch/ia64/xen/xensetup.c --- a/xen/arch/ia64/xen/xensetup.c Tue Aug 08

import include/asm-ia64/xen/interface.h to introduce introduce definitions necessary for ia64/xen hypercalls. They are basic structures to communicate with xen hypervisor and will be used later. Cc: Robin Holt <holt at sgi.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony" <tony.luck at

import include/asm-ia64/xen/interface.h to introduce introduce definitions necessary for ia64/xen hypercalls. They are basic structures to communicate with xen hypervisor and will be used later. Cc: Robin Holt <holt at sgi.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony" <tony.luck at

On Tue, 2007-08-21 at 06:23 -0600, Alex Williamson wrote: > On Tue, 2007-08-21 at 14:58 +0800, Duan, Ronghui wrote: > > Hi > > > > In current changeset.,qemu copy data uses memcpy_words, which copies 4 > > bytes at once if the length is larger than 4. This causes unaligned > > reference and leads to a performance downgrade. The issue met in > > rtl8139

Hi, Keir, Attached are the necessary changes in control panel to support ia64/vti domain builder. One is in common side, and the other is in vti specific image builder. Please take a look, and if no objection, I''d like to ask Dan''s help to check into xen-ia64-unstable.hg first. Signed-off-by Ke Yu <ke.yu@intel.com> Signed-off-by Anthony Xu <anthony.xu@intel.com>

This issue only happened on creating VTI domain in IPF platform. Creating IA32 or IA32E VMX domain is okay. Best Regards, Yongkang (Kangkang) 永康 >-----Original Message----- >From: xen-ia64-devel-bounces@lists.xensource.com >[mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of Zhang, >Jingke >Sent: 2006年10月11日 16:35 >To: xen-ia64-devel@lists.xensource.com

Hi Keir, This patch updates the ia64 buildconfigs, enabling pcifront for all kernels and pciback for -xen and -xen0. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 4833dc75ce4d buildconfigs/linux-defconfig_xen0_ia64 --- a/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28 17:52:57 2006 +0100 +++ b/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28

>From: Keir Fraser >Sent: 2006年4月28日 21:57 >On 28 Apr 2006, at 10:14, Isaku Yamahata wrote: > >> Unfortunately no. >> Roughly init_mm is only used to map vmalloc area on Linux/ia64. >> init_mm of Linux/ia64 doesn''t map the area of [PAGE_OFFSET, ...]. >> Traversing init_mm with a virtual address of the area >> gives a zero-filled pte entry.

Hi, This set of patches remarkably accelerates IDE PIO on HVM/IA64. I got a throughput of 2.11MB/sec in disk read performance. Without it, it was only 64kB/sec. I posted the prototype once. http://lists.xensource.com/archives/html/xen-devel/2006-12/msg00077.html The basic idea is to add a buffering mechanism in a hypervisor. I know this approach is not sophisticated. But there is no other good

Hi Keir: IA64 has used foreign mapping interface like IA32, so this patch is not need. Pls don’t check in it. Sorry for the inconvenience. Good good study,day day up ! ^_^ -Wing(zhang xin) OTC,Intel Corporation ________________________________ From: Zhang, Xing Z Sent: 2006年12月5日 11:15 To: xen-devel@lists.xensource.com; Keir Fraser Subject: [xen-devel][Patch] add auto

On Fri, 2008-04-04 at 13:29 +0100, Xen staging patchbot-linux-2.6.18-xen wrote: > # HG changeset patch > # User Keir Fraser <keir.fraser@citrix.com> > # Date 1207312068 -3600 > # Node ID 0d6c9c975eaee85e35d4007b1b84cafbfbb24378 > # Parent 51f1b31888b8173dc9a94e46280f83c9011c4f51 > linux/x86: fix powering off certain machines > > Dell''s Precision490, for

Tags: patch fixed-upstream Patch below allows this package to be built on ia64. Xen has supported ia64 since ~3.0.1. Thanks, Alex diff -urN a/xen-3.0-3.0.4-1/debian/arch/defines b/xen-3.0-3.0.4-1/debian/arch/defines --- a/xen-3.0-3.0.4-1/debian/arch/defines 2007-07-17 12:40:58.000000000 -0600 +++ b/xen-3.0-3.0.4-1/debian/arch/defines 2007-07-17 12:41:17.000000000 -0600 @@ -5,3 +5,4 @@

Hi Keir: I spotted some bogus uses of the noreturn keyword on ia64. [IA64]: noreturn cannot be used if function may return The functions die_if_kernel and vmx_die_if_kernel can certainly return. This disqualifies them from using the noreturn keyword which is reserved for functions that never return. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Cheers, -- Visit Openswan at

>From: Isaku Yamahata >Sent: 2006年3月14日 10:12 >> > > Comments, Keir (or others)? >> > >> > Sounds like the proper fix. I''ll leave it to Christian and others >> > involved in the Linux upstreaming effort to have the final word. >> >> Comments, Christian (or others)? Any chance this will get into >> 3.0.2? Certainly it should

Hi Keir, The CS# 17131 which I write for bind guest to NUMA node via cpu affinity missed one condition existing in some machines, where there aren''t any cpus but only memories. Under this condition it will fail to set cpu_affinity because of none parameter. I cope with this condition in the new patch and make a little change of the methods to find suitable node to bind guest. When