Re: [XenPPC] Re: xm-test

2006-09-14 Thread Tony Breeds
On Fri, Sep 15, 2006 at 12:10:44PM +1000, Tony Breeds wrote: > This patch gets the process further, but I expect more changes to be > required. See I said therie'd be more. With this additional patch, the initrd.img and the rootfs build successfully. (available from http://bakeyournoodle.com/~to

[XenPPC] [linux-ppc-2.6] [POWERPC][XEN] should call HYPERVISOR_poll() not HYPERVISOR_block()

2006-09-14 Thread Xen patchbot-linux-ppc-2 . 6
# HG changeset patch # User Jimi Xenidis <[EMAIL PROTECTED]> # Node ID 5a609aa8489bcb45a7e22f90526c52278025c5bc # Parent 4a1f58739bc25b80eae92af80b9ef309cb25468c [POWERPC][XEN] should call HYPERVISOR_poll() not HYPERVISOR_block() block will enable interrupts, this is a bad thing to do while in ud

[XenPPC] Re: xm-test

2006-09-14 Thread Tony Breeds
On Thu, Sep 14, 2006 at 04:23:48PM -0400, Jimi Xenidis wrote: > Tony expressed interest xm-test.. > I was in a really looong boring meeting so figured I just try it. > > anyway.. started a wiki page to at least list the packges I needed to > get it started. > http://wiki.xensource.com/xenwiki/

[XenPPC] [PATCH] SMP support

2006-09-14 Thread Amos Waterland
Enable secondary processors as schedulable entities and allow domU's to run on them. Tested extensively on JS20 and JS21 with up to ten domains at a time. Note that this patch relies on the hdec storm patch just posted. Signed-off-by: Amos Waterland <[EMAIL PROTECTED]> --- setup.c | 36

[XenPPC] [PATCH] Fix infinite loop caused by hdec storm

2006-09-14 Thread Amos Waterland
This was the cause of the periodic hang on secondary processors that has been holding back the submission of the SMP patch. Signed-off-by: Amos Waterland <[EMAIL PROTECTED]> --- time.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -r c94df1e4e62c xen/arch/powerpc/time.c --- a/x

[XenPPC] [PATCH] Improved tracing facility

2006-09-14 Thread Amos Waterland
This is not a real tracing facility, but it is good enough to find bugs. It supports symbolic lookup and tracepoint insertion, as well as hooking the three main entry points to the hypervisor. Signed-off-by: Amos Waterland <[EMAIL PROTECTED]> --- arch/powerpc/exceptions.c| 79 +++

[XenPPC] Assertion 'entry->next->prev == entry' failed

2006-09-14 Thread Amos Waterland
With current linux.hg and xen.hg, I am getting this consistently when creating my third domU: (XEN) Domain[2].0: initializing (XEN) Assertion 'entry->next->prev == entry' failed, line 92, file xen/include/xen/list.h (XEN) BUG at xen/include/xen/list.h:92

Re: [XenPPC] DomU panic when accessing ramdisk

2006-09-14 Thread Hollis Blanchard
On Thu, 2006-09-14 at 17:52 -0400, poff wrote: > > I haven't seen this. Could you describe your platform (including memory, > > steps to reproduce, bug frequency), and attach your xm config file and > > boot log to a bug report please? > > http://bugzilla.xensource.com/bugzilla/, and assign to me.

Re: [XenPPC] DomU panic when accessing ramdisk

2006-09-14 Thread poff
> I haven't seen this. Could you describe your platform (including memory, > steps to reproduce, bug frequency), and attach your xm config file and > boot log to a bug report please? > http://bugzilla.xensource.com/bugzilla/, and assign to me. Submitted, please let me know if need additional info

Re: [XenPPC] DomU panic when accessing ramdisk

2006-09-14 Thread Hollis Blanchard
On Thu, 2006-09-14 at 15:22 -0400, poff wrote: > Following the wiki for creating a domain, and using ramdisk.image.gz from > Amos, > usually get the following panic... DomU is then repeatedly restarted, see xm > list > also console output at end. > > One time I got the 'Bad page state in process

[XenPPC] [xenppc-unstable] [XEND][POWERPC] fix tabs that snuck in

2006-09-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch # User [EMAIL PROTECTED] # Node ID c94df1e4e62c7ab04faf05c8c5586f050f6513fd # Parent 14e7c2948115b2f7ba82e37df571447c0428b8e5 [XEND][POWERPC] fix tabs that snuck in Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]> --- tools/python/xen/xend/FlatDeviceTree.py | 10 +---

[XenPPC] xm-test

2006-09-14 Thread Jimi Xenidis
Tony expressed interest xm-test.. I was in a really looong boring meeting so figured I just try it. anyway.. started a wiki page to at least list the packges I needed to get it started. http://wiki.xensource.com/xenwiki/XenPPC/Run/XM-Test tools/xm-test/README tells you what you need to do,

[XenPPC] [xenppc-unstable] [XEN][POWERPC] support non-RMA memory in domU

2006-09-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch # User Hollis Blanchard <[EMAIL PROTECTED]> # Node ID 14e7c2948115b2f7ba82e37df571447c0428b8e5 # Parent 3d60bf30dff21fec2fdc8a931c725c23508cb94c [XEN][POWERPC] support non-RMA memory in domU - domU device tree now gets two /memory nodes; the first is the RMA - the tools now ca

Re: [XenPPC] 128 meg domU???

2006-09-14 Thread Hollis Blanchard
On Fri, 2006-09-01 at 14:07 -0500, Hollis Blanchard wrote: > > It sounds like Jimi wants to convince me that our domain memory > allocation path (i.e. increase_reservation) should be different from > everybody else's. Right now he's tracking non-RMA memory (for dom0 only) > in large-page-sized "ex

Re: [XenPPC] JS20 hangs while 'Quiescing Open Firmware ...'

2006-09-14 Thread poff
>> SOL is broken on the 'older model' bladecenters - this has nothing >> to do with Xen, >> ie SOL does not work at all, Xen or not. >> >> When I place the blade in a newer bladecenter, SOL works ok. > sorry to keep beating on this, but is this some early access > bladecenter, you have a model

[XenPPC] DomU panic when accessing ramdisk

2006-09-14 Thread poff
Following the wiki for creating a domain, and using ramdisk.image.gz from Amos, usually get the following panic... DomU is then repeatedly restarted, see xm list also console output at end. One time I got the 'Bad page state in process 'swapper''... as described in wiki. However, the 'Bad page'

[XenPPC] [xenppc-unstable] [POWERPC][XEN] Clean up init_frame_table()

2006-09-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch # User Jimi Xenidis <[EMAIL PROTECTED]> # Node ID 3d60bf30dff21fec2fdc8a931c725c23508cb94c # Parent 1eed6129bd9a15d3bf58f9cc88ed2535506c11e2 [POWERPC][XEN] Clean up init_frame_table() figure out its size correctly and remove unused global Signed-off-by: Jimi Xenidis <[EMAIL

[XenPPC] [xenppc-unstable] [XEN][POWERPC] Better whitespace fix.

2006-09-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch # User Hollis Blanchard <[EMAIL PROTECTED]> # Node ID 1eed6129bd9a15d3bf58f9cc88ed2535506c11e2 # Parent 4fd80d78e227877b5319b09e6befe54e0c6906c9 [XEN][POWERPC] Better whitespace fix. Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]> --- xen/include/asm-powerpc/page.h |6

[XenPPC] [xenppc-unstable] [XEN][POWERPC] Whitespace.

2006-09-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch # User Hollis Blanchard <[EMAIL PROTECTED]> # Node ID 4fd80d78e227877b5319b09e6befe54e0c6906c9 # Parent daa613b3f42362ff97e6712f5318a0bd0a6e1291 [XEN][POWERPC] Whitespace. Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]> --- xen/arch/powerpc/powerpc64/ppc970.c |8 -

[XenPPC] [xenppc-unstable] [XEN][POWERPC] Fix build break.

2006-09-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch # User Hollis Blanchard <[EMAIL PROTECTED]> # Node ID daa613b3f42362ff97e6712f5318a0bd0a6e1291 # Parent a1beb7b142226b2d00af68806e02cba6100e6aa3 [XEN][POWERPC] Fix build break. Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]> --- xen/arch/powerpc/of-devtree.h |1 + 1 f

[XenPPC] [xenppc-unstable] [POWERPC][XEN] break out the ppc970.c functionality

2006-09-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch # User Jimi Xenidis <[EMAIL PROTECTED]> # Node ID 164572d15e60079b8fe93b0f675312f5553c7163 # Parent 25442712f4cb2de72b1dd9dbdb471942c84ceca3 [POWERPC][XEN] break out the ppc970.c functionality getting way to crowded in there. Signed-off-by: Jimi Xenidis <[EMAIL PROTECTED]> -

[XenPPC] [xenppc-unstable] [POWERPC][XEN] Better explane the larx/stcx issue with interrupts

2006-09-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch # User Jimi Xenidis <[EMAIL PROTECTED]> # Node ID 25442712f4cb2de72b1dd9dbdb471942c84ceca3 # Parent 1d50658481071d73564b4d722e3d3199104c481a [POWERPC][XEN] Better explane the larx/stcx issue with interrupts Signed-off-by: Jimi Xenidis <[EMAIL PROTECTED]> --- xen/arch/powerpc

[XenPPC] [xenppc-unstable] [POWERPC][XEN] add ofd_strstr() that checks all strings from an OF property

2006-09-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch # User Jimi Xenidis <[EMAIL PROTECTED]> # Node ID a1beb7b142226b2d00af68806e02cba6100e6aa3 # Parent 164572d15e60079b8fe93b0f675312f5553c7163 [POWERPC][XEN] add ofd_strstr() that checks all strings from an OF property Some OF properties can have a list of '\0' terminated strin

Re: [XenPPC] JS20 hangs while 'Quiescing Open Firmware ...'

2006-09-14 Thread Segher Boessenkool
SOL is broken on the 'older model' bladecenters - this has nothing to do with Xen, ie SOL does not work at all, Xen or not. When I place the blade in a newer bladecenter, SOL works ok. There might be a management module firmware update that fixes this for your older bladecenter. Segher __

Re: [XenPPC] JS20 hangs while 'Quiescing Open Firmware ...'

2006-09-14 Thread Jimi Xenidis
On Sep 14, 2006, at 10:23 AM, poff wrote: SOL is broken on our older model bladecenter. To be clear, this is a problem with _your_specific_ blade center or "older models" if you can use SOL to talk to your linux console without Xen and you cannot _with_ Xen then we need to get to the bottom

Re: [XenPPC] JS20 hangs while 'Quiescing Open Firmware ...'

2006-09-14 Thread poff
>> SOL is broken on our older model bladecenter. > To be clear, this is a problem with _your_specific_ blade center or > "older models" > if you can use SOL to talk to your linux console without Xen and you > cannot _with_ Xen then we need to get to the bottom of that. SOL is broken on the 'o

Re: Hang on boot Was: [XenPPC] [xenppc-unstable] [POWERPC][XEN] Detect bad spurious interrupt condition and panic instead of hang

2006-09-14 Thread Jimi Xenidis
Yup Tony, thats it. Beofre actually detecting this panic we uses to just "hang" with the last of the buffered output showing that Linux was processing the dt_* tree (IIRC), now at least the panic flushed out put and shows you why. -JX On Sep 14, 2006, at 3:11 AM, Tony Breeds wrote: On Tue

Re: Hang on boot Was: [XenPPC] [xenppc-unstable] [POWERPC][XEN] Detect bad spurious interrupt condition and panic instead of hang

2006-09-14 Thread Tony Breeds
On Tue, Sep 12, 2006 at 06:00:17PM +0200, Segher Boessenkool wrote: > >Sometimes when Xen is booted and we let Linux init the MPIC for > >"the second time" Xen could end up in a loop where the CPU is > >constantly being interrupted by the MPIC. > > > >Because of console buffering, the last mess