On 06/27/2012 07:27 PM, Jan Kiszka wrote:
> Instead of flushing pending coalesced MMIO requests on every vmexit,
> this provides a mechanism to selectively flush when memory regions
> related to the coalesced one are accessed. This first of all includes
> the coalesced region itself but can also applied to other regions, e.g.
> of the same device, by calling memory_region_set_flush_coalesced.
>
> +
> +void memory_region_clear_flush_coalesced(MemoryRegion *mr)
> +{
> + qemu_flush_coalesced_mmio_buffer();
> + mr->flush_coalesced_mmio = false;
> +}
This will clear the implicit flag set by set_coalesced, but also any
explicit flag set by set_flush_coalesced. In some convoluted setup that
will never happen, this can cause breakage. This can be addresses
either using two flags (or perhaps using the coalesced list for the
implicit flag) or by a comment in clear_coalesced's documentation.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
