From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Timothy J. Moore" <Timothy.Moore@expidas.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Weidong Han <weidong.han@intel.com>
Subject: Re: RE: VT-d support proprietary NVidia/ATI GPU passthrough
Date: Mon, 22 Feb 2010 11:48:31 -0500 [thread overview]
Message-ID: <20100222164831.GA8921@phenom.dumpdata.com> (raw)
In-Reply-To: <E5E913F540B51B4C997F7A2993168735BC95981B0A@vmdc1.w3host.co.uk>
On Mon, Feb 22, 2010 at 12:32:48PM +0000, Timothy J. Moore wrote:
> How can xen implement these vendor specific resets? How could we find out the gfx vendor specific stuff?
>
> Can we take anything from the opensource NV, nouveau, or Gallium3D drivers?
As I understand it, the reason for the FLR is to re-initialize the video
cards to re-run through the basic ROM code. Pretty much exactly the same
thing that is done during machine startup. But for gfx pass-through you
need to this with the Bochs code running so it can call the gfx BIOS.
I don't think that the open-source drivers go so low to re-initialize
the card?
Thought perhaps another way to do this, is to put the cards in D3 (cold)
state and then re-initialize them back up? (this is btw, what the
pciback drivers does when it seizes the card).
next prev parent reply other threads:[~2010-02-22 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 8:12 [PATCH 1/3] VT-d: support Intel IGD passthrough Han, Weidong
2010-02-04 17:08 ` Ian Jackson
2010-02-05 1:52 ` Weidong Han
2010-02-18 9:49 ` Isaku Yamahata
2010-02-20 7:47 ` Weidong Han
[not found] ` <E5E913F540B51B4C997F7A2993168735BC95981B01@vmdc1.w3host.co.uk>
2010-02-22 7:07 ` VT-d support proprietary NVidia/ATI GPU passthrough Weidong Han
2010-02-22 12:32 ` Timothy J. Moore
2010-02-22 16:48 ` Konrad Rzeszutek Wilk [this message]
2010-02-23 1:16 ` Weidong Han
2010-02-23 21:08 ` Timothy J. Moore
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=20100222164831.GA8921@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Timothy.Moore@expidas.net \
--cc=weidong.han@intel.com \
--cc=xen-devel@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.