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: William Pitcock <nenolod@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Nvidia drivers on Xen with dom0 pvops on ultra-recent "git tip"kernel on x86_64
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Mon, 27 Apr 2009 17:07:17 -0700
Cc: Andrew Lyon <andrew.lyon@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Nigel Gamble <nigel@xxxxxxx>
Delivery-date: Mon, 27 Apr 2009 17:07:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1240816930.4387.18.camel@petrie>
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> <1240816930.4387.18.camel@petrie>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090320)
William Pitcock wrote:
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.

get_phys_to_machine is no problem, but I'm curious about why it needs set_phys_to_machine.

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.

In theory the driver shouldn't need to special case any code; the normal driver API functions should do the right things in both cases. Could you go into a bit more detail about what your needs are?


Xen-devel mailing list