search for: xenppc

This is an important find, it may require an audit of uses list_del where its use is not immediately by some form of destruction of the containing object. -JX On Sep 21, 2006, at 6:21 PM, Amos Waterland wrote: > I believe it is the case that if the last element of a list is deleted > with list_del(), and then the list is scanned with list_empty(), > undefined results can occur. The

(CCed to xen-devel for completeness. ;) On Wed, 2006-08-16 at 17:24 +0200, Tristan Gingold wrote: > I am porting xen-ppc''s xencomm to xen/ia64. > Currently on xen/ia64 copy_from/to_guest uses guest virtual address. This > works well as long as the virtual addresses are in the TLB. When not in TLB > (or vTLB) the hypercall can''t success without domain help. The

changeset: 11011:b60ea69932b1 tag: tip parent: 11010:e4f1519b473f parent: 10999:15304ad81c50 user: kfraser@localhost.localdomain date: Wed Aug 9 12:04:20 2006 +0100 summary: Merge with xenppc-unstable. Hardware: x460 NOTE: This runs were done with the latest version of Harry''s disk.iso patch. ******************** x86_32(no PAE): *************************** * dom0: SLES10 GM * dom0 boots fine * xend starts without problem --- Linux HVM domain status: --- * Xm-test compl...

Hi All, We are planning to support the XEN on IBM PowerPC 970MP based blade which is running SUSE 10 Operating System. We have couple of queries regarding support XEN: 1. Is there any readily available patch for SUSE 10(as a guest) to support paravertualization? 2. Is there any porting required for XEN source for IBM 970MP? 3. Is it support both paravertualization and Hypervisor ?, If yes,

> > > New to xen. > > Does Xen run on the Power PC architecture? Specifically G5.. I see some > > info on the web sites but i haven''t seen anything > > that tells me it''s ready and supported. > > > > If Xen does in fact run on a G5 processor would i be able to install a > > windows O/S as a Domain guest O/S on it? > > Since

Hi, We are trying to set up XEN testbed on Thamesblue Supercomputer which has IBM JS20 Blades. I compiled the SLOF firmware from the source on one of the blade. The compilation went smooth and generated the following binaries *boot_rom.bin boot_rom_bimini.bin* When we try to flash boot_rom.bin firmware binary then we get the following error: * update_flash: RTAS: validate() Invalid candidate

Hi, We are trying to set up XEN testbed on Thamesblue Supercomputer which has IBM JS20 Blades. I compiled the SLOF firmware from the source on one of the blade. The compilation went smooth and generated the following binaries *boot_rom.bin boot_rom_bimini.bin* When we try to flash boot_rom.bin firmware binary then we get the following error: * update_flash: RTAS: validate() Invalid candidate

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were