From: Weidong Han <weidong.han@intel.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Mr. Teo En Ming (Zhang Enming)" <space.time.universe@gmail.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Jean Guyader <jean.guyader@gmail.com>
Subject: Re: Xen 4.0.0 first release candidate / graphics passthru
Date: Thu, 21 Jan 2010 18:24:29 +0800 [thread overview]
Message-ID: <4B582B5D.5020803@intel.com> (raw)
In-Reply-To: <20100121095551.GN2861@reaktio.net>
Pasi Kärkkäinen wrote:
> On Thu, Jan 21, 2010 at 05:52:15PM +0800, Weidong Han wrote:
>
>> Jean Guyader wrote:
>>
>>> 2010/1/21 Pasi Kärkkäinen <pasik@iki.fi>:
>>>
>>>
>>>> On Thu, Jan 21, 2010 at 09:09:35AM +0000, Jean Guyader wrote:
>>>>
>>>>
>>>>> 2010/1/21 Pasi Kärkkäinen <pasik@iki.fi>:
>>>>>
>>>>>
>>>>>> On Tue, Jan 12, 2010 at 10:05:12AM +0000, Keir Fraser wrote:
>>>>>>
>>>>>>
>>>>>>> On 12/01/2010 09:32, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>> Does 4.0 include gpu passthru features? If not are there any updated
>>>>>>>>>> patches to try gpu passthru with 4.x?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> There is support (c/s 20144).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Btw is it possible now to specify a file to load the VGA bios from?
>>>>>>>> earlier it was required to hardcode it into some header file or so.
>>>>>>>>
>>>>>>>>
>>>>>>> I think it is hardcoded that qemu will take a copy of the host system's BIOS
>>>>>>> (i.e., for the primary host VGA). Other options would be easy to implement
>>>>>>> I'm sure, if someone's interested.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> I was just looking at same older mails, and it seems for example Teo En Ming
>>>>>> and others who got Xen VGA passthrough working had to copy the vgabios-pt.bin
>>>>>> to tools/firmware/vgabios/ before building Xen.
>>>>>>
>>>>>> That's not very practical..
>>>>>>
>>>>>>
>>>>>>
>>>>> Right now the code copy the bios from 0xC0000. So if you want to pass through
>>>>> a secondary display adapter with the vga bios you are not copying the right one,
>>>>> that why this hack was for.
>>>>> Surely the code could be modified to add an option to copy the bios of
>>>>> the right card.
>>>>>
>>>>>
>>>>>
>>>> Ok, thanks for the info.
>>>>
>>>> Do I remember correctly that there was a problem with copying the BIOS from some cards,
>>>> or on some setups? And that's why the patch to load it from a file was made?
>>>>
>>>>
>>>>
>>> Yes, I think that was because of that, and I'm not sure about the
>>> intel IGD but I think that was causing some issue.
>>> The code could have a cleanup and use sysfs to get the rombios, if I
>>> works with the intel graphic card I think we should do that.
>>>
>>> Jean
>>>
>>>
>> vbios copied from 0xC0000 doesn't work for some graphics cards, e.g.
>> Nvidia GS 8400, due to the vbios code is modified after initialization.
>> So it needs to load it from file. yes, it's not practical, Intel IGD
>> cards don't have this issue in our tests. One possible good solution is
>> to load vbios from expansion ROM of graphics cards, but we found
>> expansion ROM address are invalid for some graphics cards, even using
>> Linux upstream. It needs to look into Linux code.
>>
>>
>
> So at this point should be add two things:
>
> 1) option in guest cfgfile telling from which card to copy the vbios from
>
I think adding an option in guest config file to indicate primary or
secondary gfx assignment can cover this.
> 2) option to load the vbios from a file specified in guest cfgfile
>
I don't prefer this. It involves much manual work for users. It's better
to find a general solution which is also easy to use.
Regards,
Weidong
> How does that sound like?
>
> -- Pasi
>
>
next prev parent reply other threads:[~2010-01-21 10:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 7:33 Xen 4.0.0 first release candidate Keir Fraser
2010-01-12 8:34 ` Andrew Lyon
2010-01-12 9:06 ` Keir Fraser
2010-01-12 9:32 ` Xen 4.0.0 first release candidate / graphics passthru Pasi Kärkkäinen
2010-01-12 10:05 ` Keir Fraser
2010-01-21 8:54 ` Pasi Kärkkäinen
2010-01-21 9:09 ` Jean Guyader
2010-01-21 9:12 ` Pasi Kärkkäinen
2010-01-21 9:18 ` Jean Guyader
2010-01-21 9:52 ` Weidong Han
2010-01-21 9:55 ` Pasi Kärkkäinen
2010-01-21 10:24 ` Weidong Han [this message]
2010-01-21 10:28 ` Pasi Kärkkäinen
2010-01-21 12:10 ` Sander Eikelenboom
2010-01-21 12:50 ` Weidong Han
2010-01-21 12:56 ` Pasi Kärkkäinen
2010-01-21 13:03 ` Weidong Han
2010-01-21 14:02 ` Keir Fraser
2010-01-21 14:11 ` Pasi Kärkkäinen
2010-01-21 14:23 ` Pasi Kärkkäinen
2010-01-21 19:53 ` Timothy J. Moore
2010-01-22 2:37 ` Weidong Han
2010-01-22 2:22 ` Weidong Han
2010-01-22 22:15 ` Timothy J. Moore
2010-01-23 11:12 ` Han, Weidong
2010-01-25 14:09 ` Keir Fraser
2010-01-26 1:52 ` Weidong Han
2010-01-12 9:47 ` Xen 4.0.0 first release candidate gilberto nunes
2010-01-12 10:06 ` Keir Fraser
2010-01-12 10:25 ` Pasi Kärkkäinen
2010-01-12 10:50 ` gilberto nunes
2010-01-12 11:01 ` Keir Fraser
2010-01-12 11:14 ` gilberto nunes
2010-01-12 11:31 ` Sassy Natan
2010-01-12 11:38 ` Keir Fraser
2010-01-12 11:48 ` Sassy Natan
2010-01-12 11:51 ` Keir Fraser
2010-01-12 12:02 ` Pasi Kärkkäinen
2010-01-15 0:54 ` Stefan Kuhne
2010-01-15 1:17 ` Stefan Kuhne
2010-01-15 1:19 ` Zhigang Wang
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=4B582B5D.5020803@intel.com \
--to=weidong.han@intel.com \
--cc=jean.guyader@gmail.com \
--cc=keir.fraser@eu.citrix.com \
--cc=pasik@iki.fi \
--cc=space.time.universe@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 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).