Re: [XenPPC] XenPPC IEEE1275 binding?

2006-08-09 Thread Segher Boessenkool
I remember seeing some mention of it, but I don't think we currently have an IEEE1275 binding describing the contents of the /xen node. As you're currently both the only producer and the only consumer of this node, you don't need a real binding yet. But, the standard properties you have should

Re: [XenPPC] [PATCH/RFC] Support Xen console=comX option

2006-08-10 Thread Segher Boessenkool
I had an error in my logic that was caching the package-to-path conversion. Also, the exit condition from the loop walking the peer list should be zero or negative. Thanks to Jimi for pointing this out. SLOF is not broken :) Oh it is, just not in this aspect ;-) Segher

Re: [XenPPC] XenPPC IEEE1275 binding?

2006-08-10 Thread Segher Boessenkool
We intend to include these in the OpenPAPR :-P Heh have fun. start-info is going away, which means we'll need to add more properties to replace it... something like this: xen { name = xen; version = Xen-3.0-unstable; Call this property xen-version

Re: [XenPPC] PHDR link failure testcase

2006-08-16 Thread Segher Boessenkool
Perhaps, this is just mythology/warm-n-fuzzy for me, but I really like having 1 PHDR. Lemmy collect my thoughts and come up with a rational reason. 1 PHDR works just as well; the important thing is to explicitly define your PHDRs in the linker script. Segher

Re: [XenPPC] Error creating domain on JS20 (Fw: [Prose-jvm] Brief Status in TRL (2006/08/24))

2006-08-24 Thread Segher Boessenkool
The directory does not exist in my dom0 Linux, but PowerPC, [EMAIL PROTECTED] exists instead. Maybe, my JS20 is newer than Watson's, and uses different CPU (970FX). Today, I have no time to debug this further. Any solution? You have a newer SLOF version, only the ancient version uses

Re: [XenPPC] Error creating domain on JS20 (Fw: [Prose-jvm] Brief Status in TRL (2006/08/24))

2006-08-25 Thread Segher Boessenkool
I also probably have a old blade. But your statement is correct: Almost all JS20. However, that is not the same as all the JS20. Yes indeed. We hardly ever test on those old machines; there's not many of them around. So you're our tester now, heh. Don't worry: you found one of the two

Re: [XenPPC] [PATCH/RFC] Schedule idle domain on secondary processors

2006-08-29 Thread Segher Boessenkool
It is quite stable in that the secondary processors reliably join the idle domain and wait for free pages to scrub, handling 0x980 interrupts with no problem. What's this 980 exception? However, the domU's sometimes hang during initialization. When the domU hangs, it seems the whole

Re: [XenPPC] [PATCH/RFC] Schedule idle domain on secondary processors

2006-08-29 Thread Segher Boessenkool
It is quite stable in that the secondary processors reliably join the idle domain and wait for free pages to scrub, handling 0x980 interrupts with no problem. What's this 980 exception? Perhaps my phrasing is bad. I was referring to the hypervisor decrementor interrupt (hdec). Ah yes, I

Re: [XenPPC] [PATCH/RFC] Schedule idle domain on secondary processors

2006-08-29 Thread Segher Boessenkool
This patch check-stops my box. For those of you with Maples, the 405 console spits out those nasty: Error: Magic number in message area NVRAM is not valid. errors. This is proof (well, a strong indicator, heh) that the U4 is indeed hung. Segher

Re: [XenPPC] [PATCH/RFC] Schedule idle domain on secondary processors

2006-08-29 Thread Segher Boessenkool
Most common cause of this is hanging the U3/U4. Do you have a hardware debugger to see where this happens? It's been my experience that RISCWatch isn't very helpful in these situations (e.g. can't stop the processor). When the northbridge goes, JTAG becomes unhappy. Works fine for me,

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

2006-09-12 Thread Segher Boessenkool
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 message you see is some message from early kernel boot. Anyway.. we detect this now

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] [PATCH] Print backtrace on BUG

2006-09-21 Thread Segher Boessenkool
Hi Amos, +do { \ +unsigned long sp, lr, pc, tp; \ You can do without tp: +asm(mr %0, 1 : =r (sp)); \ +asm(mflr %0 : =r

Re: [XenPPC] [PATCH] Print backtrace on BUG

2006-09-21 Thread Segher Boessenkool
Bah, it's too early for GCC asm: +asm(mr %0, 1 : =r (sp)); \ +asm(mflr %0 : =r (lr)); \ +asm(mflr %0; bl 1f; 1: mflr %1; mtlr %0 : =r (tp), =r (pc));\ asm(bl $+4 ; mflr %0; mtlr %1

Re: [XenPPC] [xenppc-unstable] [XEN][POWERPC] SCOM access is fully known and working

2006-09-21 Thread Segher Boessenkool
+/* these give iface errors because the address is ambiguous after + * the above bit dropping */ +BUG_ON(addr == 0x8000); Anything with the high bit set isn't available via SCOMC/SCOMD, only via the external interfaces. +/* WARNING! older 970s (pre FX) shift the bits right

Re: [XenPPC] Help with JS21 disk solution

2006-09-25 Thread Segher Boessenkool
@@ -126,6 +126,8 @@ static void u4_inv_entry(ulong pgn) union dart_ctl dc; ulong retries = 0; +return u4_inv_all(); If you need inv_all here, you have a bug elsewhere... Segher ___ Xen-ppc-devel mailing list

Re: [XenPPC] Help with JS21 disk solution

2006-09-27 Thread Segher Boessenkool
If you need inv_all here, you have a bug elsewhere... I agree, I'm just trying to corner the beast :) Ok, this seems to work, its pretty solid, so somehow our invalidation logic is sufficient for network but not disk activity. One theory is that disk uses short lived TCE entries and

Re: [XenPPC] Cannot boot from local disk

2006-10-06 Thread Segher Boessenkool
Good question, I think it may do iso-9660 and fat16, and I heard that ext2 might be supported, but I'd be surprised if SLOF can do reiserfs It can do ext2/ext3 and fat12/fat16 (both versions)/fat32. The various CD and DVD filesystems are next on the list of filesystems we want to support,

Re: [XenPPC] Spurious interrupt count

2006-10-07 Thread Segher Boessenkool
One day, all mpic operations will happen in Xen, Ah, you got me worried already. But this MPIC-sharing architecture is temporary, good :-) Segher ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com

Re: [XenPPC] [linux-ppc-2.6] [LINUX][XEN][POWEPRC] def config changes

2006-10-26 Thread Segher Boessenkool
Why did you change the date? Jimi did not change the date by hand. The Kconfig logic discussed above did so, and I believe that the myriad benefits of that logic outweigh the cost of resolving the trivial merge conflict caused by the date. Perhaps we can investigate removing the date

Re: [XenPPC] [PATCH] Remove timestamp from xen_maple_defconfig

2006-10-26 Thread Segher Boessenkool
Doesn't this require that everybody build like this all the time? In that case, I'm not sure a one-time checkin makes sense. Yes. You can edit your Makefile's to always include it, if you want. Segher ___ Xen-ppc-devel mailing list

Re: [XenPPC] Re: [Xen Wiki] Update of XenPPC/Run by JeroneYoung

2006-11-01 Thread Segher Boessenkool
+ SLOTH firmware loads up. You will PXE boot the Xen image built putting an example of the command line to enter when using Sloth. I was It's not called SLOTH, it's SLOF :-) Segher ___ Xen-ppc-devel mailing list

Re: [XenPPC] [PATCH] Flush the ERAT early for secondary CPUs

2006-11-09 Thread Segher Boessenkool
p = probability of success = .997 (897 / 900) q = probability of failure = .003 (1.0 - .997) n = number of trials = 2323 X = number of successes= 2323 Applying these to the binomial probability formula, we get: P(2323) = 2323! / ((2323 - 2323)! * 2323!) * .997**2323 * .003**

Re: [XenPPC] [PATCH] Disable DPM until code is audited

2006-12-02 Thread Segher Boessenkool
Most JS20 and JS21 have DPM disabled on the board, What does this mean? SLOF/js2x enables DPM always, for example; there is no hardware override that I'm aware of. According to S9.9 of 970FX UM: Dynamic power management can be disabled in the RAS units by asserting bit[0] in the JTAG

Re: [XenPPC] [PATCH] Disable DPM until code is audited

2006-12-04 Thread Segher Boessenkool
-/* FIXME Do not set the NAP and DPM bits in HID0 until we have had a - * chance to audit the safe halt and idle loop code. */ +/* FIXME Do not set the NAP bit in HID0 until we have had a chance + * to audit the safe halt and idle loop code. */ hid0.bits.nap = 0; /*

Re: [XenPPC] Machine check: instruction-fetch TLB tablewalk

2006-12-17 Thread Segher Boessenkool
[NOTE: I'm assuming the decode here is correct] (XEN) MACHINE CHECK: IS Recoverable (XEN) SRR1: 0x000cf032 (XEN) 0b11: Exception caused by a hardware uncorrectable (XEN) error (UE) detected while doing a reload of an (XEN) instruction-fetch TLB tablewalk. (XEN) (XEN)

Re: [XenPPC] Re: OF claim untrustworthy?

2007-01-10 Thread Segher Boessenkool
Repeated identical claims cause an unknown exception at the Forth prompt, but don't succeed. I'm not sure if that becomes an error via the client interface. It does, the throw method would return an OF failure, this is expected. The OF side of the specific client interface call has to

Re: [XenPPC] [xenppc-unstable] [XEN][POWERPC] Linker script simplification broke optimized builds.

2007-01-23 Thread Segher Boessenkool
[XEN][POWERPC] Linker script simplification broke optimized builds. offending changeset was: changeset: 14126:c759c733f77d So put it back and just update the symbols like a good little boy. What, you're replacing one bug by a big bag of other bugs? Wouldn't it have been smarter to just fix

Re: [XenPPC] [PATCH 1/3] libxc: add start_info_t node to devtree

2007-01-24 Thread Segher Boessenkool
This patch creates a new node, /xen/start_info_t in the flat devtree. Could you name it start-info or something similar to be more in line with normal device tree naming conventions? Segher ___ Xen-ppc-devel mailing list

Re: [XenPPC] [PATCH] Linux shim code for ACM hypercalls

2007-06-04 Thread Segher Boessenkool
This patch provides the implementation of the shim layer for ACM hypercalls on PPC. Signed-off-by: Stefan Berger [EMAIL PROTECTED] -ENOPATCH Segher ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com