From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Nvidia Reverse <aidivnreverse@gmail.com>
Cc: Gordan Bobic <gordan@bobich.net>, xen-devel@lists.xen.org
Subject: Re: GTX 760 passed through
Date: Mon, 2 Dec 2013 15:16:20 -0500 [thread overview]
Message-ID: <20131202201620.GA17961@phenom.dumpdata.com> (raw)
In-Reply-To: <CACryO-5eR4zPmfs-qyJMJLqn=aZFQ6bLhUFFR1dtdvaMRaG2YA@mail.gmail.com>
On Mon, Dec 02, 2013 at 06:36:48PM +0100, Nvidia Reverse wrote:
> The nvlddmkm.sys needs to be patched removing the whitelist for the device
> ids allowed to be virtualized.
> But the interesting part is how NVIDIA detects that the GPU is
> virtualized...
Interesting. I was thinking that the BIOS/firmware would run itself
in the virtualized or non-virtualized code depending on the device id.
But you seem to imply that it is all in the OS driver code.
At which point the idea of just modifying in QEMU the PCI device ID
to be different would .. well, make it possible to do a lot of
neat stuff as Gordan pointed out.
In terms of legal issues of patching up a windows kernel driver and
showing other folks how to do it?
No idea. Presumarily there is some license thing that you had agreed
when you installed the Nvidia driver - check to see what it says.
>
>
> On Mon, Dec 2, 2013 at 5:12 PM, Gordan Bobic <gordan@bobich.net> wrote:
>
> > On Mon, 2 Dec 2013 13:18:22 +0100, Nvidia Reverse <aidivnreverse@gmail.com>
> > wrote:
> >
> >> Hello,
> >> I've successfully passed a unmodified GTX 760 to Win7 x64. It involved
> >> some driver patching on the client side but I'm close to getting the
> >> required steps on the server side, too. Are there any legal issues
> >> that might arise from releasing a patch?
> >>
> >
> > Considering we have everything up to and including a Titan/780 easily
> > modifiable into Quadros/Teslas/Grids to make them work? :)
> >
> > I for one would welcome not having to break out my soldering iron.
> >
> > When you say driver patching, what are we talking about? Unless
> > something changed very recently, just modifying the .inf file
> > isn't sufficient (unless your server-side patch does some
> > device ID faking - which it probably doesn't since the card
> > is still showing up as a 780 in domU).
> >
> > Gordan
> >
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-12-02 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 12:18 GTX 760 passed through Nvidia Reverse
2013-12-02 16:12 ` Gordan Bobic
2013-12-02 17:36 ` Nvidia Reverse
2013-12-02 20:16 ` Konrad Rzeszutek Wilk [this message]
2013-12-02 21:04 ` Gordan Bobic
2013-12-03 16:09 ` Konrad Rzeszutek Wilk
2013-12-03 16:56 ` Gordan Bobic
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=20131202201620.GA17961@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=aidivnreverse@gmail.com \
--cc=gordan@bobich.net \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).