From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Boris Derzhavets <bderzhavets@yahoo.com>
Cc: Michael Ralston <michael@ralston.id.au>,
xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Re: [Xen-users] pv_ops kernel and nvidia binary driver
Date: Tue, 14 Jul 2009 12:52:06 -0700 [thread overview]
Message-ID: <4A5CE1E6.2010503@goop.org> (raw)
In-Reply-To: <701488.94378.qm@web56101.mail.re3.yahoo.com>
On 07/11/09 23:03, Boris Derzhavets wrote:
> A while ago Jeremy responded the same question.
> Per Jeremy:- unmodified binary Nvidia driver would crash under Xen.
> Modified driver should in the pvops kernel.
>
> It's also my major concern as well.
>
> Boris
>
> --- On *Sun, 7/12/09, Michael Ralston /<michael@ralston.id.au>/* wrote:
>
>
> From: Michael Ralston <michael@ralston.id.au>
> Subject: [Xen-users] pv_ops kernel and nvidia binary driver
> To: xen-users@lists.xensource.com
> Date: Sunday, July 12, 2009, 1:48 AM
>
> Just wondering what it will take to get the nvidia binary driver
> working on a pv_ops kernel.
>
> It makes it difficult to debug without the source to the nvidia
> driver, but I think it should be possible to get it to work without
> changing the binary driver. If the dom0 kernel had access to all the
> resources that a bare metal kernel did, then it should work right?
>
The problem comes down to whether the nvidia driver assumes the kernel's
(pseudo-)physical addresses are really machine physical or not. If it
doesn't do the appropriate conversions between physical and machine
addresses using the standard Linux DMA API (or similar), then it will
end up misprogramming the hardware and reading/writing random memory.
There's not a lot we can do about that if that happens within the binary
part of the nvidia driver. If the binary code calls out to the
source-available parts of the driver to do those conversions, then it
would be possible to fix there.
There are other potential pitfalls the nvidia driver could be falling
into, but that's the most likely.
J
next prev parent reply other threads:[~2009-07-14 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 6:03 pv_ops kernel and nvidia binary driver Boris Derzhavets
2009-07-14 19:52 ` Jeremy Fitzhardinge [this message]
2009-07-15 8:14 ` Re: [Xen-users] " Ian Campbell
2009-07-15 16:57 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2009-07-14 21:43 Boris Derzhavets
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A5CE1E6.2010503@goop.org \
--to=jeremy@goop.org \
--cc=bderzhavets@yahoo.com \
--cc=michael@ralston.id.au \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.