Avi Kivity wrote:
Anthony Liguori wrote:
I think the current VT-d code needs some reworking.
We should build the table as the shadow page table gets built. We
should suppress iotlb flushes unless the table is actually being
updated.
We can't, since we need the iommu tables populated before we issue any
dma.
Yes, as I've mentioned, the lack of a DMA window notification API can be
handled as a special case.
Perhaps we want something like MAP_POPULATE for shadow, which would
then affect the iommu tables. Userspace would then do:
mlock()
... set up device assignment
ioctl(..., KVM_POPULATE)
Exactly like this :-)
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
