Re: [Xen-devel] 2.6.30 dom0 Xen patches

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

The schema bellow has been tested positive on Core2Duo E8400,
E6600 boxes and caused dropping into stack trace
when loading under Xen 3.4.1-rc6 Hypervisor on Q9550 box.
What reminds an issue had been raised up for PVOPS kernel
in march or april 2009 and finally, fixed by Jeremy Fitzhradinge.
However , building kernel without changing dependency
with CONFIG_SPARSE_IRQ=y in .config file allows to load
kernel on Q9550 box under Xen 3.4.1 as well as on Core2Duo
boxes.

Boris.

--- On Tue, 7/7/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] 2.6.30 dom0 Xen patches
To: "Andrew Lyon" <andrew.lyon@xxxxxxxxx>, "Jan Beulich" <JBeulich@xxxxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Tuesday, July 7, 2009, 1:12 PM

To build xenified 2.6.30.1 via Andy's 2.6.30 pacth set in it's current state :-

1. Created log1 via script
rm -f log1
touch -f log1
for V in `ls 6*`
do
echo $V >> log1
cat $V|grep CONFIG_SPARSE_IRQ >> log1
done

2. Analyzed log1

60035_xen3-patch-2.6.29.patch1
+# if !defined(CONFIG_SPARSE_IRQ) && NR_CPUS < MAX_IO_APICS
+# elif defined(CONFIG_SPARSE_IRQ) && 8 * NR_CPUS > 32 * MAX_IO_APICS
+#ifdef CONFIG_SPARSE_IRQ
+#ifdef CONFIG_SPARSE_IRQ
+#ifdef CONFIG_SPARSE_IRQ
+#ifdef CONFIG_SPARSE_IRQ
+#ifdef CONFIG_SPARSE_IRQ
+#ifdef CONFIG_SPARSE_IRQ
+#ifndef CONFIG_SPARSE_IRQ

60036_xen3-patch-2.6.30.patch1
-# if !defined(CONFIG_SPARSE_IRQ) && NR_CPUS < MAX_IO_APICS
-# elif defined(CONFIG_SPARSE_IRQ) && 8 * NR_CPUS > 32 * MAX_IO_APICS
+# elif defined(CONFIG_SPARSE_IRQ)


3. Made global replacement CONFIG_SPARSE_IRQ by CONFIG_GENERIC_HARDIRQS in files
60035_xen3-patch-2.6.29.patch1,60036_xen3-patch-2.6.30.patch1

4.Untared kernel-2.6.30.1 tar.bz2 and applied patches. Built 2.6.30.1 xenified kernel with no errors

Loaded Xen 3.4.1-rc6 Dom0 with xenified 2.6.30.1 (been built) on top of Ubuntu 9.04 Server
Tested OSOL 2009.06 loaded with PV Drivers in stub domain OK , also tested OSOL 2009.06 PV DomU and F11 PV DomU.

Boris


--- On Thu, 7/2/09, Jan Beulich <JBeulich@xxxxxxxxxx> wrote:

From: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] 2.6.30 dom0 Xen patches
To: "Andrew Lyon" <andrew.lyon@xxxxxxxxx>
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Thursday, July 2, 2009, 2:53 AM

>>> Andrew Lyon <andrew.lyon@xxxxxxxxx> 01.07.09 19:15 >>>
>I have rebased the xen-patches from opensuse
>kernel-source-2.6.30-50.1.src.rpm so that they can be applied to
>vanilla 2.6.30, the usual patches tarball and gentoo ebuild are
>available at http://code.google.com/p/gentoo-xen-kernel/downloads/list
>, if you are not using Gentoo simply apply the patches in numeric
>order.
>
>Some notes:
>
>both dom0 and domU require CONFIG_SPARSE_IRQ=y and CONFIG_HOTPLUG=y
>64 bit dom0/domU requires CONFIG_IA32_EMULATION=y

May I ask why you found the first and third ones to be necessary? Unless
it's because of the conditional in the loop right after the commen "Zap
stats across IRQ changes of use." in unbind_from_irq(), which I fixed a
few days ago, but didn't push out to our internal repo so far. (The fix
is to change the dependency from CONFIG_SPARSE_IRQ to
CONFIG_GENERIC_HARDIRQS in the 2.6.30 patch.)

The second one seems less meaningful, as I wouldn't think anyone would
build a general use (Xen) kernel with EMBEDDED=y, and HOTPLUG is not
user selectable without EMBEDDED.

May I also ask for you to let us know about fixes to the patches that you
find necessary which aren't just due to you applying them to plain 2.6.30?

Thanks, Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

-----Inline Attachment Follows-----

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel