All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weidong Han <weidong.han@intel.com>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH 0/3] VT-d: support Intel IGD passthrough
Date: Mon, 08 Feb 2010 11:27:14 +0800	[thread overview]
Message-ID: <4B6F8492.6000300@intel.com> (raw)
In-Reply-To: <f4527be1002060451o699c4b95xa5ead06fd4888370@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1990 bytes --]

Andrew Lyon wrote:
> On Fri, Feb 5, 2010 at 2:11 AM, Han, Weidong <weidong.han@intel.com> wrote:
>   
>> Current Xen only supports to pass-through primary gfx card. The secondary gfx pass-through patch is not in Xen yet. I think it needs to think more clearly about secondary gfx pass-through usage and implementation.
>>
>> Regards,
>> Weidong
>>     
>
> Do you have a patch for secondary passthru on Xen 4? I seem to recall
>   
No, we won't push this support in Xen 4, because it still needs more 
thinking about secondary gfx passthru usage and implementation.
> somebody had been successful with secondary passthru using an
> additional patch but I cannot find it.
>   
You can search subject "graphics passthrough with VT-d" in xen-devel 
mailing list. There are lots of discussion in the thread. I attached the 
mail which contains the patches for secondary gfx passthrough with some 
other hacks. You can have a try with them.

Regards,
Weidong

> I'd like to give it a try, I have one system with 2 x radeon x1950's
> and another with Quadro FX380 and GeForce 9500 GT, both currently
> running X, xen 3.4.2 with 2.6.31.12 suse patched dom0.
>
> Andy
>
>   
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Christian Tramnitz
>> Sent: Thursday, February 04, 2010 8:15 PM
>> To: xen-devel@lists.xensource.com
>> Subject: [Xen-devel] Re: [PATCH 0/3] VT-d: support Intel IGD passthrough
>>
>> Thanks for updating those patches to current xen.
>>
>> Is IGD pass-through also supposed to work when the IGD is not the
>> primary gfx card?
>>
>>
>> Best regards,
>>    Christian
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>>     


[-- Attachment #2: RE Xen-devel graphics passthrough with VT-d.msg --]
[-- Type: application/octet-stream, Size: 151040 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-02-08  3:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04  8:12 [PATCH 0/3] VT-d: support Intel IGD passthrough Han, Weidong
2010-02-04  8:24 ` Keir Fraser
2010-02-04  8:29   ` Han, Weidong
2010-02-04 12:15 ` Christian Tramnitz
2010-02-05  2:11   ` Han, Weidong
2010-02-06 12:51     ` Andrew Lyon
2010-02-08  3:27       ` Weidong Han [this message]
2010-02-13 12:52         ` Sander Eikelenboom

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=4B6F8492.6000300@intel.com \
    --to=weidong.han@intel.com \
    --cc=andrew.lyon@gmail.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.