This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Nvidia drivers on Xen with dom0 pvops on ultra-recent "g

To: Nigel Gamble <nigel@xxxxxxx>
Subject: Re: [Xen-devel] Nvidia drivers on Xen with dom0 pvops on ultra-recent "git tip"kernel on x86_64
From: William Pitcock <nenolod@xxxxxxxxxxxxxxxx>
Date: Mon, 27 Apr 2009 02:22:10 -0500
Cc: Andrew Lyon <andrew.lyon@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 27 Apr 2009 00:22:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CD18DBB0-DA6C-49E9-A74D-086F1642DFF8@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <949542.54584.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <49A46533.1070003@xxxxxxxx> <f4527be0902241351h440aa451l5684a814850446f@xxxxxxxxxxxxxx> <CD18DBB0-DA6C-49E9-A74D-086F1642DFF8@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2009-04-23 at 14:49 -0700, Nigel Gamble wrote:
> On Feb 24, 2009, at 1:51 PM, Andrew Lyon wrote:
> > On Tue, Feb 24, 2009 at 9:22 PM, Jeremy Fitzhardinge  
> > <jeremy@xxxxxxxx> wrote:
> >> Boris Derzhavets wrote:
> >>>
> >>> X-Server fails to start on GeForce 8500 GT
> >>> Attempting "startx" i get a trace back.
> >>> Does it mean , that a proper NVIDIA driver is just not available  
> >>> for the
> >>> most recent
> >>> 2.6.29-rc5 ?
> >>>
> >>
> >> Are you using the nvidia binary driver?  I would be surprised if it  
> >> worked
> >> out of the box; if changes need to be made to the binary parts, it  
> >> may not
> >> be fixable at all.
> >>
> >>   J
> >
> > I believe the current driver works with Xen because somebody outside
> > of nvidia contributed a patch, I use the nvidia binary driver with Xen
> > 3.2.1 and my custom dom0 kernel which is patched with
> > openSUSE Xen patches rebased to apply to vanilla, it works very well
> > but when pv_ops is merged into mainline the nvidia driver will
> > probably work when it is running on the bare metal but not under Xen
> > :(.
> >
> > Having said that the patch for Xen support only touched the open
> > source parts of the driver, as soon as the current problems with hvm
> > on pv_ops are fixed I will be testing pv_ops and nvidia driver and I
> > will attempt to fix any problems, my C skills are improving so I might
> > be able to figure it out.
> Did you ever figure this out?  I've just hit the same problem.  It  
> looks like the source code part of the Nvidia kernel module has the  
> code necessary to work on an old Xen Linux, but if it detects  
> CONFIG_PARAVIRT set for a pv_ops kernel, it gives up an doesn't  
> attempt to work with Xen at all.
> Nigel

I have this basically working on paravirt ops, but Jeremy's work has
some of the needed symbols as EXPORT_SYMBOL_GPL(), so that needs to be
cleaned up somehow before I can put out a patch (as I am not comfortable
in doing it yet).

Jeremy, I need get_phys_to_machine() and set_phys_to_machine() to be
changed to EXPORT_SYMBOL() for this. AFAIK, the equivilant symbols are
EXPORT_SYMBOL() in XenLinux 2.6.18.

Can you make it happen? Also, if we had a way of knowing whether or not
we are running under the hypervisor, I could ultimately make it work
with the right codepaths under both configurations.


Xen-devel mailing list