Muli Ben-Yehuda wrote:
On Tue, Jun 10, 2008 at 10:02:45AM -0500, Anthony Liguori wrote:

Why?  Wouldn't MMIO pages have to be mapped in the VT-d page table
in order to support pass-through?  It certainly can't hurt, can it?

By MMIO pages we refer to pages which are mapped (or can mapped) to
device MMIO regions. In other words, they are only relevant for host
memory accesses. VT-d mappings are used for *device* memory
accesses. I can't think of a good reason for a device to try to DMA to
such a page (where would the DMA end? There is no backing RAM), hence
the principal of least surprise says that we shouldn't map such pages
in the IOMMU page tables so that *if* the device tries to DMA to them
we will take an IOMMU fault rather than fail silently or machine check
(I've seen both happen with DMAs to MMIO regions).

If you add the MMIO page to the IOMMU table, then the behavior is going to be identical to what occurs on bare metal which IMHO is a good thing. Why jump through hoops to change what may or may not be an error condition instead of letting the natural error behavior happen? There may be some weird piece of hardware that relies on this behavior out there.

I don't think it's at all safe to assume that a slot is either
entirely MMIO or entirely RAM.  You could very easily construct a
slot that's a mix of both so if this is an attempt to skip MMIO
slots, it's broken.

How would suc a slot be constructed with the current code base? (Note
that you need Ben's direct MMIO patches to create an MMIO slot).

There is no such thing as an MMIO slot. All you would need to do is mmap(phys_ram_base + GPA, "/sys/bus/pci/.../region/0", MAP_SHARED | MAP_FIXED) and you'd have a mixed slot assuming GPA was within an existing RAM slot. Without MMU-notifiers, you'd have to do this before the guest started. With MMU-notifiers, you can do this during execution of the guest.

Regards,

Anthony Liguori

Cheers,
Muli

--
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

Reply via email to