|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] [VTD-NEO][patch 5/6] Intel VT-d/Neocleus 1:1 mregedcode
My informal tests did not show much performance degradation. It is not
easy to figure out miss rates without performance counters.
If you look at the latest vt-d spec on the web, there is a passthru
feature in the context entry which will allow passthru DMA on BDF
granularity in the future.
http://download.intel.com/technology/computing/vptech/Intel(r)_VT_for_Di
rect_IO.pdf
Allen
>-----Original Message-----
>From: Muli Ben-Yehuda [mailto:muli@xxxxxxxxxx]
>Sent: Tuesday, September 18, 2007 11:38 PM
>To: Kay, Allen M
>Cc: Keir Fraser; xen-devel@xxxxxxxxxxxxxxxxxxx; Guy Zana
>Subject: Re: [Xen-devel] [VTD-NEO][patch 5/6] Intel
>VT-d/Neocleus 1:1 mregedcode for PCI passthrough
>
>On Tue, Sep 18, 2007 at 11:32:25PM -0700, Kay, Allen M wrote:
>
>> Translation enabling is on per vt-d engine granularity - not BDF
>> granularity. Each BDF context entry can point to a different page
>> table structure.
>>
>> Setup a single 1:1 mapping structure to be used by all PV domains is
>> a good idea. I will give it a try tomorrow.
>
>I see, thanks for clarifying. That seems pretty strange... do you have
>a notion of the overhead incured by the 1-1 mapping and the average
>IOTLB hit/miss rates?
>
>Cheers,
>Muli
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|