[Xen-ia64-devel] Re: [Xen-devel] Re: [PATCH] kexec: framework and i386 (Take XIV)

2007-05-28 Thread Akio Takebe
Hi, Horms and Ian Thank you for your reply, Horms. I forgot Signed-off-by of the patch. Signed-off-by: Horms [EMAIL PROTECTED] Signed-off-by: Akio Takebe [EMAIL PROTECTED] Is the Signed-off-by OK, Horms? Best Regards, Akio Takebe [ Ian Campbell added to CC list ] On Tue, Sep 05, 2006 at

Re: [Xen-ia64-devel] Serial woes with kexec on an HP RX2620

2007-05-28 Thread Akio Takebe
Hi, Horms Hi Takebe-san, thanks a lot for all your help with this problem. With a bit of luck we now have a solution. I found that by porting kexec_disable_iosapic() to xen (which involved cut and paste only) and calling it from the right places, the serial port on the rx2620 works just fine in

Re: [Xen-ia64-devel] Serial woes with kexec on an HP RX2620

2007-05-28 Thread Horms
On Mon, May 28, 2007 at 03:37:06PM +0900, Akio Takebe wrote: Hi, Horms Hi Takebe-san, thanks a lot for all your help with this problem. With a bit of luck we now have a solution. I found that by porting kexec_disable_iosapic() to xen (which involved cut and paste only) and calling it

Re: [Xen-ia64-devel] [RFC] Warning at move_native_irq()

2007-05-28 Thread Akio Takebe
Hi, all I could fix this issue by using CONFIG_GENERIC_PENDING_IRQ=n. What do you think the following patch? Is this too hacky? Signed-off-by: Akio Takebe [EMAIL PROTECTED] Best Regards, Akio Takebe Hi, I met the following WARN_ON(1) when I booted smp domU of RHEL5. This message is occurred

Re: [Xen-ia64-devel] [RFC] Warning at move_native_irq()

2007-05-28 Thread Akio Takebe
Hi, I'm sorry. This patch seems to happen another issue. Please ignore it. Best Regards, Akio Takebe Hi, all I could fix this issue by using CONFIG_GENERIC_PENDING_IRQ=n. What do you think the following patch? Is this too hacky? Signed-off-by: Akio Takebe [EMAIL PROTECTED] Best Regards,

[Xen-ia64-devel] [PATCH]fix initialization order of buddy allocator

2007-05-28 Thread Daisuke Nishimura
Hi, Machines with multi NUMA nodes may panic on bootup. Attached patch(for C/S15145), in which I modified the initialization order of buddy allocator, fixes this problem. I tested booting dom0/domVTi and kernel-make on guests. Any comments and feedbacks would be appreciated. I will describe the

Re: [Xen-ia64-devel] [PATCH]fix initialization order of buddy allocator

2007-05-28 Thread Isaku Yamahata
On Mon, May 28, 2007 at 07:48:51PM +0900, Daisuke Nishimura wrote: Machines with multi NUMA nodes may panic on bootup. Attached patch(for C/S15145), in which I modified the initialization order of buddy allocator, fixes this problem. I tested booting dom0/domVTi and kernel-make on guests.

[Xen-ia64-devel] PATCH: reimplement vcpu_get_psr

2007-05-28 Thread Tristan Gingold
Hi, almost the same as before, but without the slowdown! Tristan. # HG changeset patch # User Tristan Gingold [EMAIL PROTECTED] # Date 1180358348 -7200 # Node ID b23c25c8b8253ebf76386224ae68c1f0374b1ebf # Parent 6bfc805a83e5961fe2879e61822e905bb0b22980 Reimplement vcpu_get_psr. It now returns

Re: [Xen-ia64-devel] PATCH: rewrite vcpu_get_psr

2007-05-28 Thread Alex Williamson
On Mon, 2007-05-28 at 14:53 +0200, Tristan Gingold wrote: On Thu, May 10, 2007 at 02:15:34PM -0600, Alex Williamson wrote: On Wed, 2007-05-09 at 06:10 +0200, Tristan Gingold wrote: Hi, a stripped-down version of a previous patch: reimplement vcpu_get_psr. Should be a noop, I

Re: [Xen-ia64-devel] PATCH: rewrite vcpu_get_psr

2007-05-28 Thread Tristan Gingold
On Mon, May 28, 2007 at 07:30:54AM -0600, Alex Williamson wrote: However I don't understand your figures: how can real time be less than user time ? Isn't real time the elapsed time ? Parallel build, -j4. The real time is the elapsed time, user is cumulative across all 4 CPUs. Thanks,

[Xen-ia64-devel] PATCH: vcpu_set_psr

2007-05-28 Thread Tristan Gingold
Hi, this patch creates vcpu_set_psr, which is called by vcpu_rfi. Tested by compiling the kernel, without time regression. Tristan. # HG changeset patch # User Tristan Gingold [EMAIL PROTECTED] # Date 1180365232 -7200 # Node ID fb9d9383c3e60a16c68c5bd73446e7c4cd2c8c14 # Parent

[Xen-ia64-devel] IA64 Intel further problems

2007-05-28 Thread Radek Antoniuk
Hi! I've overcame the problem with the blank screen. The reason was that there was wrong path in the vmm= section in the elilo.conf file :) Now, there is something more. I've compiled into kernel all modules needed for booting, created an initrd image even. The problem is that, that the

[Xen-ia64-devel] Re: IA64 Intel further problems

2007-05-28 Thread Radek Antoniuk
Device Boot Start End Blocks Id System /dev/sda1 1446335841015 ee EFI GPT One more thing. The message says also : unknown fs on block(8,2). Why 8 ? The 2 is for the sda2. But I'm not sure if 8 is proper number. Radek

Re: [Xen-ia64-devel] IA64 Intel further problems

2007-05-28 Thread Radek Antoniuk
Alex Williamson napisaƂ(a): On Mon, 2007-05-28 at 18:13 +0200, Radek Antoniuk wrote: image=/boot/vmlinuz-2.6.18-4-mckinley label=Linux root=/dev/sda2 read-only initrd=/boot/initrd.img-2.6.18-4-mckinley image=/boot/vmlinuz-2.6.18-xen label=xen

Re: [Xen-ia64-devel] IA64 Intel further problems

2007-05-28 Thread Alex Williamson
On Mon, 2007-05-28 at 19:04 +0200, Radek Antoniuk wrote: Well. Not all drivers, but the needed for the FS mounting :) Indeed parted showed the partitions: Disk /dev/sda: 36.7GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End SizeFile system Name

[Xen-ia64-devel] Re: [Xen-devel] Re: [PATCH] kexec: framework and i386 (Take XIV)

2007-05-28 Thread Horms
On Mon, May 28, 2007 at 03:25:04PM +0900, Akio Takebe wrote: Hi, Horms and Ian Thank you for your reply, Horms. I forgot Signed-off-by of the patch. Signed-off-by: Horms [EMAIL PROTECTED] Signed-off-by: Akio Takebe [EMAIL PROTECTED] Is the Signed-off-by OK, Horms? Actually, i think

Re: [Xen-ia64-devel] [PATCH]fix initialization order of buddy allocator

2007-05-28 Thread Daisuke Nishimura
Hi, Yamahata-san. Thank you for your comments. BTW your signed-off-by is missing. Sorry. I forgot it. And I attach the patch again. Signed-off-by: Daisuke Nishimura [EMAIL PROTECTED] 2. The xenheap area (from xen_pstart to xenheap_phys_end) must exist in node0 from its design? (As far