similar to: XenLinux/IA64 domU forward port

Recipe for useing xen/ia64 with pv_ops domU. Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Randy Dunlap <randy.dunlap at oracle.com> --- Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 183 insertions(+), 0 deletions(-) create mode 100644

Recipe for useing xen/ia64 with pv_ops domU. Signed-off-by: Akio Takebe <takebe_akio at jp.fujitsu.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Randy Dunlap <randy.dunlap at oracle.com> --- Documentation/ia64/xen.txt | 183 ++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 183 insertions(+), 0 deletions(-) create mode 100644

On Thu, Feb 21, 2008 at 11:33:16PM -0600, Robin Holt wrote: > On Fri, Feb 22, 2008 at 02:10:19PM +0900, Isaku Yamahata wrote: > > Xenlinux/ia64 needs to reserve one more region passed from xen hypervisor > > as start info. > > > > Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> > > --- > > include/asm-ia64/meminit.h | 7 +++++++ > >

On Thu, Feb 21, 2008 at 11:33:16PM -0600, Robin Holt wrote: > On Fri, Feb 22, 2008 at 02:10:19PM +0900, Isaku Yamahata wrote: > > Xenlinux/ia64 needs to reserve one more region passed from xen hypervisor > > as start info. > > > > Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> > > --- > > include/asm-ia64/meminit.h | 7 +++++++ > >

>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.

Yes, like real Linux/ia64, it is not possible to run the same Xenlinux bits both on ski and on real hardware. A different configuration and build is required. The config difference is the same as it was with the privified xenlinux... I think you did that successfully before (with privified xenlinux) so give that config file a try and if it doesn''t work, let me know. BTW, I think I know

BTW, the xenlinux-2.6.11.bk''s version is: ChangeSet@1.2085, 2005-05-12 11:10:24-06:00, djm@kirby.fc.hp.com More work on hyperprivops Signed-off-by: Dan Magenheimer <dan.magenheimer@hp.com> Thanks, Kevin >-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Tian, Kevin >Sent: Friday,

This is the patch from Amos Waterland for the xenconsole to use /dev/xvc0 instead of taking over ttys. I''ve fixed a few places which needed to check for XVC mode in addition to serial mode. Also, until LANANA responds with an official minor, I''ve adjusted it to use char 250/187 (in the experimental range) as opposed to 204/187 Signed-off-by: Jeremy Katz

The patched attached enables x86_64 xenlinux with "late pin, early unpin", which is already implemented for x86_32. Since we now only pin the root rather than any of the other levels, the overall performance became better especially with workloads that require heavy memory management operations. On 8-way x86_64 xenlinux (dom0) the kernel build was improved by about 10% (using make

Hi, Keir, Any comments upon following patch? ;-) We need it to further check in a specific configuration file (likely xen0_defconfig_ia64tiger) later to run xen on IA64 tiger box. Currently we have no generic one for all IA64 boxes. Let''s know if better way to do it. Currently custom with tiger box can only get that file out of the tree. Thanks, Kevin >-----Original Message-----

I have always needed the rm_nx_xd patch to boot Xen / Dom0 on the ES7000 x86_64 but the system boots without any issues on plain vanilla Linux 2.6. > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of Keir Fraser > Sent: Thursday, August 18, 2005 4:49 AM > To: Nakajima, Jun > Cc: Jerone Young;

Hello, I''m trying to build XenLinux 2.4.30 on debian. I get the following error for make linux24 make[2]: *** No rule to make target `skbuff.c'',needed by `/usr/src/xen-2.0/linux-2.4.30-xen0/include/linux/modules/skbuff.ver''. Stop. Could somebody help me resolve this error. Or if this is some problem with the system configuration that I''m using, could

I have a data frame with two columns, one of which is a factor (Species) and the other is numeric (BA, which stands for basal area). Here's a sample: Species BA ACSA 55.7632696 FRAM 122.9933524 ACSA 67.54424205 ACSA 89.22123136 ACSA 82.46680716 ACSA 22.46238747 ACSA 19.94911335 ACSA 20.42035225 ACSA 19.00663555 ACSA 21.67698931 ACSA 57.80530483 ACSA 30.31636911 Dead 43.98229715 Dead

[Added CC:virtualization at lists.linux-foundation.org] On Mon, Feb 18, 2008 at 11:28:41AM +0800, Dong, Eddie wrote: > Hi, Tony & all: > Recently Xen-IA64 community is considering to add paravirt_ops > support to keep sync with X86 and reduce maintenance effort. With > pv_ops, sensitive instructions or some high level primitive > functionalities (such as MMU ops) are replaced

[Added CC:virtualization at lists.linux-foundation.org] On Mon, Feb 18, 2008 at 11:28:41AM +0800, Dong, Eddie wrote: > Hi, Tony & all: > Recently Xen-IA64 community is considering to add paravirt_ops > support to keep sync with X86 and reduce maintenance effort. With > pv_ops, sensitive instructions or some high level primitive > functionalities (such as MMU ops) are replaced

This is the patch from Amos Waterland for the xenconsole to use /dev/xvc0 instead of taking over ttys. I''ve fixed a few places which needed to check for XVC mode in addition to serial mode. Also, until LANANA responds with an official minor, I''ve adjusted it to use char 250/187 (in the experimental range) as opposed to 204/187. (Should be identical to this patch from last

Hi have 4 dom0 with debian lenny running xen. When I run ps axf|grep xvd I see it''s different on diferent dom0s. dom0-A 15677 ? S< 0:00 \_ [blkback.139.xvd] 15678 ? S< 0:38 \_ [blkback.139.xvd] 17015 ? S< 0:00 \_ [blkback.140.xvd] 17016 ? S< 2:34 \_ [blkback.140.xvd] 21309 ? S< 0:00 \_ [blkback.142.xvd] 21310 ?

On Fri, May 14, 2010 at 09:10:57PM +0200, Peter Klar wrote: > As the bug seems to be related to the SLAB allocator, the dump says ''kernel > BUG at mm/slub.c:2969!'', I also recompiled the kernel using the SLAB instead > of SLUB allocator, but this does not make any difference, the behaviour is > the same (beside the dump then reports a bug within slab.c instead of

On Fri, May 14, 2010 at 09:10:57PM +0200, Peter Klar wrote: > As the bug seems to be related to the SLAB allocator, the dump says ''kernel > BUG at mm/slub.c:2969!'', I also recompiled the kernel using the SLAB instead > of SLUB allocator, but this does not make any difference, the behaviour is > the same (beside the dump then reports a bug within slab.c instead of

Hola: Con esto del R me da la impresión que avanzo un paso y retrocedo dos! El caso es que tengo una "cascada de funciones", para realizar un análisis descriptivo "automático" en función del tipo de variable. Y en los resultados, en lugar de aparecer el nombre de la variable, aparece el nombre del argumento. Esto ocurre tanto si utilizo o no la función get(). Un ejemplo