[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-devel] [PATCH][RFC]Move PCI Configuration Spacesfrom Dom0 to Xen
- To: "Espen Skoglund" <espen.skoglund@xxxxxxxxxxxxx>, "Haitao Shan" <maillists.shan@xxxxxxxxx>
- From: "Shan, Haitao" <haitao.shan@xxxxxxxxx>
- Date: Fri, 11 Apr 2008 08:42:49 +0800
- Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "Han, Weidong" <weidong.han@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
- Delivery-date: Thu, 10 Apr 2008 17:47:25 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcibK7jL/4c6fPYgQLS2/1/dfyco8QAPz55g
- Thread-topic: [Xen-devel] [PATCH][RFC]Move PCI Configuration Spacesfrom Dom0 to Xen
Actually I do not find a clear explanation in MCH specification on this.
Luckily, dom0's kernel does not write 0xcf8 without valid bit set.
Does access to 0xCFC return data based on the last valid latched data in 0xCF8,
or last latched data without valid bit set in 0xCF8?
Inl(0xcfc); <----This is skipped? Or data at 00:00.0 register 0.
Another question is:
Inb(0xcfd); <----This is skipped? Or data at 00:00.0 register 1?
Can you tell me where do you find these answers? Thanks!
From: Espen Skoglund [mailto:espen.skoglund@xxxxxxxxxxxxx]
Sent: 2008年4月11日 0:55
To: Haitao Shan
Cc: Keir Fraser; Shan, Haitao; Tian, Kevin; xen-devel; Kay, Allen M; Jiang,
Yunhong; Han, Weidong
Subject: Re: [Xen-devel] [PATCH][RFC]Move PCI Configuration Spacesfrom Dom0 to
I believe dword writes to 0xCF8 should always be latched into the
internal shadow register, irrespective of whether the enable bit (bit
31) is set. Accesseses to 0xCFC can then safely be skipped if enable
bit in latch register is not set.
> Thanks, Keir!
> 2008/4/10, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>:
>> On 10/4/08 10:45, "Shan, Haitao" <haitao.shan@xxxxxxxxx> wrote:
>> This patch will move reading and writing of PCI configuration
>> spaces from dom0 to Xen. It also changes VTD code, so that they can
>> touch the PCI configuration spaces with proper lock.
>> This will also benefit MSI support in Xen.
>> Can you give some comments? Thanks!
>> The approach is fine. I will read it more thoroughly, clean it up a bit if
>> necessary, and certainly check it in.
>> -- Keir
>> Xen-devel mailing list
> -------------- next part --------------
> An HTML attachment was scrubbed...
Xen-devel mailing list