[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen PV IOMMU interface draft C

> Xen PV IOMMU hypercall interface
> --------------------------------
> A two argument hypercall interface (do_iommu_op).
>     ret_t do_iommu_op(XEN_GUEST_HANDLE_PARAM(void) arg, unsigned int count)
> First argument, guest handle pointer to array of `struct pv_iommu_op`
> Second argument, unsigned integer count of `struct pv_iommu_op` elements in 
> array.

Is there an upper limit on it?  If there is an we hit, what is the return
value? Should it be E2BIG and the toolstack (or kernel) should adjust size

.. snip..
> Linux kernel architecture
> =========================
> The Linux kernel will use the PV-IOMMU hypercalls to map its PFN address
> space into the IOMMU. It will map the PFNs to the IOMMU address space using
> a 1:1 mapping, it does this by programming a BFN to GFN mapping which matches
> the PFN to GFN mapping.
> The native SWIOTLB will be used to handle devices which cannot DMA to all of
> the kernel's PFN address space.

native? Or the Xen SWIOTLB which consult the P2M space? In which case it is
the Xen-SWIOTLB.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.