WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Experimental results for VGA passthrough

To: "Beng Heng, Ng" <bengheng@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Experimental results for VGA passthrough
From: Jean Guyader <jean.guyader@xxxxxxxxx>
Date: Tue, 9 Jun 2009 23:28:16 +0100
Cc: Andrew Lyon <andrew.lyon@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 09 Jun 2009 15:28:40 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=s9q08cmN9fhifMlnqwcyMbjf3vaa9e/fdcmvPCNWJRI=; b=iaNnBbaHgyCv14ZdQMdHnnqiEQfwuVpnt4GbkkRCgD843i99lz/Y+8uSjxlmEBg4UJ WMlcRr7/2LTRsYuCDQQ8Rspc4+6c6ECmWrd8cww/01qx5sfAQgjwSfbskJoKQlyap6it 39B9mD7sadZs/uSpXW3RaO4dLsKKIdSrmwzk8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ZmdUHMhwOt11tdLcAzj5Zaa1cNAvESheX/JS5M3+0GZec8xwjpx+uQmXJbO8jlJe01 emaTozvgE+OpFSygS/KeBBeLdIW1FZ1WrdrdVsmhT6g2IlJXWDwK8npwNwLR/n6F09aR rVF544pCgSpTD+WHgzkxljwcGtuGWN8q67r5w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A2D3A07.5040105@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4A27FFB0.6060108@xxxxxxxxxxxxxx> <fdaac4d50906062042s35d003efv3cd64e2228b639ce@xxxxxxxxxxxxxx> <4A2CA37B.4060206@xxxxxxxxxxxxxx> <f4527be0906080129o3f6dcbafh42a1e0a6b714ea54@xxxxxxxxxxxxxx> <4A2D1748.8070007@xxxxxxxxxxxxxx> <f4527be0906080719u3cc985c3v739010d47cce60c9@xxxxxxxxxxxxxx> <4A2D1F58.4000001@xxxxxxxxxxxxxx> <f68b66460906080911l581a938ai7e78cf1f33d74304@xxxxxxxxxxxxxx> <4A2D3905.4030302@xxxxxxxxxxxxxx> <4A2D3A07.5040105@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Yes, here are the value we need to fake and the raison why:
  - GMCH, when the vgabios execute at actually check this register in
the host bridge (bdf 0:0.0, offset 0x52). On the intel platform this
register is there to identify the amount of stolen memory and
therefore the supported resolution in legacy mode (VGA/VESA).
  - VID/DID. Linux check that. If it doesn't match with the graphic
card it doesn't reconise the chipset and doesn't create the agpgart.
  - OpRegion address. Not sure about this one, but when you
shutdown/sleep vista if this value is present the driver will try to
save some information in a ACPI NVS region.

All those register are public you can find some more information about
those here:
www.intel.com/Assets/PDF/datasheet/319970.pdf

Jean

2009/6/8 Beng Heng, Ng <bengheng@xxxxxxxxxxxxxx>:
> Also, you mentioned earlier that we need to return some fake values to
> the host bridge. Would appreciate if you could explain, or refer me to
> some writeups on this. Thanks.
>
> - Beng Heng
>
> Beng Heng, Ng wrote:
>> Could you elaborate? Thanks.
>>
>> - Beng Heng
>>
>> Jean Guyader wrote:
>>> 2009/6/8 Beng Heng, Ng <bengheng@xxxxxxxxxxxxxx>:
>>>> Uses the driver included in the patch to initialize the graphics card.
>>>> This is my own flag. I'm not sure what Jean's plans are.
>>> The intel code for qemu you've found is not made for that.
>>>
>>> Jean
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>
>

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