From: Bei Guan <gbtju85@gmail.com>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>
Subject: Re: FLR Patch for Xen 4.0
Date: Thu, 13 May 2010 10:34:00 +0800 [thread overview]
Message-ID: <AANLkTik8pIQ51QEL_Ih0K4XDc8-29wr0wAcTdOFXXxf1@mail.gmail.com> (raw)
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B21E8193F6@shsmsx501.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1967 bytes --]
Hi,
Have you test the nVidia Geforce 8400 GS PCI Express x16 in xen4.0, which
Mr. Teo Enming have test in xen 3.5-unstable branch wich some patch.
http://lists.xensource.com/archives/html/xen-devel/2009-08/msg01013.html
Thanks a lot!
2010/5/10 Han, Weidong <weidong.han@intel.com>
> If the device doesn’t support FLR capability, there will be a default
> reset for it, e.g. Dstate transition. But it doesn’t guarantee to work. For
> your ATI card, we didn’t try with it. Likely it cannot work. nVidia Quadro
> FX 3800 and IGD on Intel platforms (e.g. Q35 and Q45) were tested and works
> on current Xen upstream. Some other gfx cards may work with extra patches
> (e.g. 1:1 map vBAR and pBAR). There were many emails to discuss it in
> xen-devel mailing list, you’d better to find and read those emails.
>
>
>
> Regards,
>
> Weidong
>
>
>
> *From:* Bei Guan [mailto:gbtju85@gmail.com]
> *Sent:* Monday, May 10, 2010 4:53 PM
> *To:* Han, Weidong
> *Cc:* Xen Devel
> *Subject:* Re: [Xen-devel] FLR Patch for Xen 4.0
>
>
>
> My VGA hardware is as following. Can I find a patch to make it support pci
> passthrough?
>
> #lspci
> ……
> 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD
> 3450
>
>
> Xen4.0 can not support the ATI adapters defaultly, is it? Because my VGA
> passthrough can not work correctly.
>
>
>
> 2010/5/10 Han, Weidong <weidong.han@intel.com>
>
> There were several patches checked into xen for pci passthru, you can find
> relevant code in tools/python/xen/xend/server/pciif.py.
>
>
>
> Regards,
>
> Weidong
>
>
>
> *From:* xen-devel-bounces@lists.xensource.com [mailto:
> xen-devel-bounces@lists.xensource.com] *On Behalf Of *Bei Guan
> *Sent:* Monday, May 10, 2010 3:44 PM
> *To:* Xen Devel
> *Subject:* [Xen-devel] FLR Patch for Xen 4.0
>
>
>
> Hi,
>
> Is there a FLR patch for xen 4.0 PCI Passthrought ?
> Thanks.
>
> gavin
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 4942 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-13 2:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 7:44 FLR Patch for Xen 4.0 Bei Guan
2010-05-10 8:26 ` Han, Weidong
2010-05-10 8:52 ` Bei Guan
2010-05-10 9:04 ` Han, Weidong
2010-05-13 2:34 ` Bei Guan [this message]
2010-05-13 2:37 ` Han, Weidong
2010-05-13 7:02 ` Bei Guan
2010-05-13 11:37 ` Pasi Kärkkäinen
2010-05-14 1:09 ` Han, Weidong
2010-05-13 7:08 ` Bei Guan
2010-05-14 1:00 ` Han, Weidong
2010-05-13 11:36 ` Pasi Kärkkäinen
2010-05-10 9:05 ` Mark Hurenkamp
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=AANLkTik8pIQ51QEL_Ih0K4XDc8-29wr0wAcTdOFXXxf1@mail.gmail.com \
--to=gbtju85@gmail.com \
--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 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).