On Thu, 2008-05-22 at 09:49 -0400, Lennart Sorensen wrote: > On Thu, May 22, 2008 at 07:12:03AM +0100, Ian Campbell wrote: > > That is true of the original Xen kernels (up to 2.6.18) but not of the > > new Xen kernels (2.6.22+). > > Is that a result of the paravirt stuff going in?
Exactly. > > The original Xen port of Linux required that you build a specific Xen > > kernel which would not boot on native and which made changes that broke > > the Nvidia drivers, hence they check for CONFIG_XEN and abort if it is > > enabled, they also added a load of #ifdef CONFIG_XEN stuff. > > > > The new Xen port of Linux use the paravirt_ops infrastructure which > > makes the support of Xen transparent to the rest of the kernel and also > > allows one binary to boot on both native and Xen. Since the Xen support > > is now transparent to the rest of the kernel both the check for > > CONFIG_XEN and the #ifdef CONFIG_XEN code is obsolete and should be > > removed from the nvidia drivers. > > I made a patch yesterday that does exactly that, and yes it works fine. > > > See http://lists.debian.org/debian-kernel/2008/05/msg00948.html for a > > report that removing all the CONFIG_XEN checks fixes the issue, it did > > for me too. > > We should have a new driver release by the weekend with this done. I sent my patch to #481161 but it seems to have disappeared somewhere along the line, I'll resend it here too. Ian. -- Ian Campbell Current Noise: System Of A Down - Chic 'N' Stew The only way to keep your health is to eat what you don't want, drink what you don't like, and do what you'd rather not. -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
