From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Shan, Haitao" <haitao.shan@intel.com>,
Espen Skoglund <espen.skoglund@netronome.com>,
Haitao Shan <maillists.shan@gmail.com>
Cc: "Han, Weidong" <weidong.han@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
xen-devel <xen-devel@lists.xensource.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>
Subject: Re: [PATCH][RFC]Move PCI Configuration Spacesfrom Dom0 to Xen
Date: Fri, 11 Apr 2008 09:24:47 +0100 [thread overview]
Message-ID: <C424DEDF.1F070%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <823A93EED437D048963A3697DB0E35DE01427F40@pdsmsx414.ccr.corp.intel.com>
I think we can safely follow qemu here and return all-1s on reads when the
enable bit in cf8 is clear. I'll make that change.
-- Keir
On 11/4/08 01:42, "Shan, Haitao" <haitao.shan@intel.com> wrote:
> 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?
> For example:
> Outl(0x80000000, 0xcf8);
> Outl(0x00000001, 0xcf8);
> Inl(0xcfc); <----This is skipped? Or data at 00:00.0 register 0.
> Another question is:
> Outl(0x80000000, 0xcf8);
> Inb(0xcfc);
> Inb(0xcfd); <----This is skipped? Or data at 00:00.0 register 1?
> Can you tell me where do you find these answers? Thanks!
>
> Shan Haitao
>
> -----Original Message-----
> From: Espen Skoglund [mailto:espen.skoglund@netronome.com]
> 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
> Xen
>
> 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.
>
> eSk
>
>
>
> [Haitao Shan]
>> Thanks, Keir!
>> 2008/4/10, Keir Fraser <keir.fraser@eu.citrix.com>:
>>>
>>> On 10/4/08 10:45, "Shan, Haitao" <haitao.shan@intel.com> 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
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>>
>>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://lists.xensource.com/archives/html/xen-devel/attachments/20080410/263aa
>> 734/attachment.htm
>
next prev parent reply other threads:[~2008-04-11 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 9:45 [PATCH][RFC]Move PCI Configuration Spaces from Dom0 to Xen Shan, Haitao
2008-04-10 10:24 ` Keir Fraser
2008-04-10 11:59 ` Haitao Shan
2008-04-10 16:54 ` Espen Skoglund
2008-04-11 0:42 ` [PATCH][RFC]Move PCI Configuration Spacesfrom " Shan, Haitao
2008-04-11 8:24 ` Keir Fraser [this message]
2008-04-11 12:08 ` [PATCH][RFC]Move PCI Configuration Spaces from Dom0 toXen Jan Beulich
2008-04-11 12:14 ` Keir Fraser
2008-04-11 14:35 ` Espen Skoglund
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=C424DEDF.1F070%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=allen.m.kay@intel.com \
--cc=espen.skoglund@netronome.com \
--cc=haitao.shan@intel.com \
--cc=kevin.tian@intel.com \
--cc=maillists.shan@gmail.com \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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.