From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
Liu Ping Fan <pingfank@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 2/5] memory: Flush coalesced MMIO on selected region access
Date: Mon, 25 Jun 2012 11:36:40 +0300 [thread overview]
Message-ID: <4FE82318.3070806@redhat.com> (raw)
In-Reply-To: <714b875f084134ae31596687651e051d4aa3c585.1340607659.git.jan.kiszka@siemens.com>
On 06/25/2012 10:00 AM, 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.
> @@ -521,6 +522,18 @@ void memory_region_add_coalescing(MemoryRegion *mr,
> void memory_region_clear_coalescing(MemoryRegion *mr);
>
> /**
> + * memory_region_set_flush_coalesced: Enforce memory coalescing flush before
> + * accesses.
> + *
> + * Ensure that pending coalesced MMIO request are flushed before the memory
> + * region is accessed. This property is automatically enabled for all regions
> + * passed to memory_region_set_coalescing() and memory_region_add_coalescing().
> + *
> + * @mr: the memory region to be updated.
> + */
> +void memory_region_set_flush_coalesced(MemoryRegion *mr);
> +
> +/**
Please provide a way to clear the flag (and autoclear on clear_coalesced).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-06-25 8:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 7:00 [PATCH 0/5] kvm: Get coalesced MMIO flushing out of the hot-path Jan Kiszka
2012-06-25 7:00 ` [PATCH 1/5] i82378: Remove bogus MMIO coalescing Jan Kiszka
2012-06-25 7:11 ` Hervé Poussineau
2012-06-25 7:15 ` Andreas Färber
2012-06-25 7:00 ` [PATCH 2/5] memory: Flush coalesced MMIO on selected region access Jan Kiszka
2012-06-25 8:36 ` Avi Kivity [this message]
2012-06-25 7:01 ` [PATCH 3/5] memory: Flush coalesced MMIO on mapping and state changes Jan Kiszka
2012-06-25 8:40 ` [Qemu-devel] " Andreas Färber
2012-06-25 8:57 ` Avi Kivity
2012-06-25 10:15 ` Jan Kiszka
2012-06-25 10:26 ` Jan Kiszka
2012-06-25 11:01 ` Avi Kivity
2012-06-25 11:13 ` Jan Kiszka
2012-06-25 7:01 ` [PATCH 4/5] VGA: Flush coalesced MMIO on related MMIO/PIO accesses Jan Kiszka
2012-06-25 7:01 ` [PATCH 5/5] kvm: Stop flushing coalesced MMIO on vmexit Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE82318.3070806@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).