|
From: | Alexey Kardashevskiy |
Subject: | Re: [Qemu-ppc] [PATCH qemu 1/5] vfio: Switch from TARGET_PAGE_MASK to qemu_real_host_page_mask |
Date: | Mon, 13 Jul 2015 17:24:17 +1000 |
User-agent: | Mozilla/5.0 (X11; Linux i686 on x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 |
On 07/13/2015 04:15 PM, David Gibson wrote:
On Fri, Jul 10, 2015 at 08:43:44PM +1000, Alexey Kardashevskiy wrote:These started switching from TARGET_PAGE_MASK (hardcoded as 4K) to a real host page size: 4e51361d7 "cpu-all: complete "real" host page size API" and f7ceed190 "vfio: cpu: Use "real" page size API" This finished the transition by: - %s/TARGET_PAGE_MASK/qemu_real_host_page_mask/ - %s/TARGET_PAGE_ALIGN/REAL_HOST_PAGE_ALIGN/ - removing bitfield length for offsets in VFIOQuirk::data as qemu_real_host_page_mask is not a macroThis does not make much sense to me. f7ceed190 moved to REAL_HOST_PAGE_SIZE because it's back end stuff that really depends only on the host page size. Here you're applying a blanket change to vfio code, in particular to the DMA handling code, and for DMA both the host and target page size can be relevant, depending on the details of the IOMMU implementation.
5/5 uses this listener for memory preregistration - this totally depends on the host page size. It was suggested to make this listener do memory preregistration too, not just DMA.
This keeps using TARGET_PAGE_MASK for IOMMU regions though as it is the minimum page size which IOMMU regions may be using and at the moment memory regions do not carry the actual page size.And this exception also doesn't make much sense to me. Partly it's confusing because the listener is doing different things depending on whether we have a guest visible IOMMU or not.
Yes...
In short, there doesn't seem to be a coherent explanation here of where the page size / alignment restriction is coming from, and therefore whether it needs to be a host page alignment, a guest page alignment, or both.Signed-off-by: Alexey Kardashevskiy <address@hidden> --- In reality DMA windows are always a lot bigger than a single 4K page and aligned to 32/64MB, may be only use here qemu_real_host_page_mask?I don't understand this question either.
The listener is called on RAM regions and DMA windows. If it is a RAM region, then host page size applies. If it is a DMA window - then 4K. So the same listener has to use different page size in different situation to check for alignments. But in reality everything will be aligned to megabytes or so. So we could enforce 64K alignment for DMA windows, for example, and make code simpler.
-- Alexey
[Prev in Thread] | Current Thread | [Next in Thread] |