From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 05/29] memory: differentiate memory_region_is_logging and memory_region_get_dirty_log_mask
Date: Tue, 26 May 2015 15:46:34 +0800 [thread overview]
Message-ID: <20150526074634.GF13749@ad.nay.redhat.com> (raw)
In-Reply-To: <1430152117-100558-6-git-send-email-pbonzini@redhat.com>
On Mon, 04/27 18:28, Paolo Bonzini wrote:
> For now memory regions only track DIRTY_MEMORY_VGA individually, but
> this will change soon. To support this, split memory_region_is_logging
> in two functions: one that returns a given bit from dirty_log_mask,
> and one that returns the entire mask. memory_region_is_logging gets an
> extra parameter so that the compiler flags misuse.
>
> While VGA-specific users (including the Xen listener!) will want to keep
> checking that bit, KVM and vhost check for "any bit except migration"
> (because migration is handled via the global start/stop listener
> callbacks).
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> hw/display/vmware_vga.c | 2 +-
> hw/virtio/dataplane/vring.c | 2 +-
> hw/virtio/vhost.c | 3 ++-
> include/exec/memory.h | 17 +++++++++++++++--
> kvm-all.c | 3 ++-
> memory.c | 7 ++++++-
> xen-hvm.c | 2 +-
> 7 files changed, 28 insertions(+), 8 deletions(-)
>
> diff --git a/hw/display/vmware_vga.c b/hw/display/vmware_vga.c
> index c17ddd1..7f397d3 100644
> --- a/hw/display/vmware_vga.c
> +++ b/hw/display/vmware_vga.c
> @@ -1124,7 +1124,7 @@ static void vmsvga_update_display(void *opaque)
> * Is it more efficient to look at vram VGA-dirty bits or wait
> * for the driver to issue SVGA_CMD_UPDATE?
> */
> - if (memory_region_is_logging(&s->vga.vram)) {
> + if (memory_region_is_logging(&s->vga.vram, DIRTY_MEMORY_VGA)) {
> vga_sync_dirty_bitmap(&s->vga);
> dirty = memory_region_get_dirty(&s->vga.vram, 0,
> surface_stride(surface) * surface_height(surface),
> diff --git a/hw/virtio/dataplane/vring.c b/hw/virtio/dataplane/vring.c
> index 5c7b8c2..e378733 100644
> --- a/hw/virtio/dataplane/vring.c
> +++ b/hw/virtio/dataplane/vring.c
> @@ -42,7 +42,7 @@ static void *vring_map(MemoryRegion **mr, hwaddr phys, hwaddr len,
> }
>
> /* Ignore regions with dirty logging, we cannot mark them dirty */
> - if (memory_region_is_logging(section.mr)) {
> + if (memory_region_get_dirty_log_mask(section.mr)) {
> goto out;
> }
>
> diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
> index 54851b7..5f698a1 100644
> --- a/hw/virtio/vhost.c
> +++ b/hw/virtio/vhost.c
> @@ -377,7 +377,8 @@ static void vhost_set_memory(MemoryListener *listener,
> memory_listener);
> hwaddr start_addr = section->offset_within_address_space;
> ram_addr_t size = int128_get64(section->size);
> - bool log_dirty = memory_region_is_logging(section->mr);
> + bool log_dirty =
> + memory_region_get_dirty_log_mask(section->mr) & ~(1 << DIRTY_MEMORY_MIGRATION);
Too long a line.
> int s = offsetof(struct vhost_memory, regions) +
> (dev->mem->nregions + 1) * sizeof dev->mem->regions[0];
> void *ram;
> diff --git a/include/exec/memory.h b/include/exec/memory.h
> index 081f7d6..229733e 100644
> --- a/include/exec/memory.h
> +++ b/include/exec/memory.h
> @@ -569,11 +569,24 @@ const char *memory_region_name(const MemoryRegion *mr);
> /**
> * memory_region_is_logging: return whether a memory region is logging writes
> *
> - * Returns %true if the memory region is logging writes
> + * Returns %true if the memory region is logging writes for the given client
> + * a bitmap of clients for which the memory region is logging writes.
I can't parse this sentence, rephrase a bit?
> *
> * @mr: the memory region being queried
> + * @client: the client being queried
> */
> -bool memory_region_is_logging(MemoryRegion *mr);
> +bool memory_region_is_logging(MemoryRegion *mr, uint8_t client);
> +
> +/**
> + * memory_region_get_dirty_log_mask: return the clients for which a
s/which a/ which the/ ?
> + * memory region is logging writes.
> + *
> + * Returns a bitmap of clients for which the memory region is logging writes.
Why repeat?
All questions are trivial enough that once you fix them or if they don't need
fixing:
Reviewed-by: Fam Zheng <famz@redhat.com>
> + * Right now this will be either 0 or (1 << DIRTY_MEMORY_VGA).
> + *
> + * @mr: the memory region being queried
> + */
> +uint8_t memory_region_get_dirty_log_mask(MemoryRegion *mr);
>
> /**
> * memory_region_is_rom: check whether a memory region is ROM
> diff --git a/kvm-all.c b/kvm-all.c
> index dd44f8c..bd1f910 100644
> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -663,7 +663,8 @@ static void kvm_set_phys_mem(MemoryRegionSection *section, bool add)
> KVMSlot *mem, old;
> int err;
> MemoryRegion *mr = section->mr;
> - bool log_dirty = memory_region_is_logging(mr);
> + bool log_dirty =
> + memory_region_get_dirty_log_mask(mr) & ~(1 << DIRTY_MEMORY_MIGRATION);
> bool writeable = !mr->readonly && !mr->rom_device;
> bool readonly_flag = mr->readonly || memory_region_is_romd(mr);
> hwaddr start_addr = section->offset_within_address_space;
> diff --git a/memory.c b/memory.c
> index e688f5e..a982d99 100644
> --- a/memory.c
> +++ b/memory.c
> @@ -1318,11 +1318,16 @@ bool memory_region_is_skip_dump(MemoryRegion *mr)
> return mr->skip_dump;
> }
>
> -bool memory_region_is_logging(MemoryRegion *mr)
> +uint8_t memory_region_get_dirty_log_mask(MemoryRegion *mr)
> {
> return mr->dirty_log_mask;
> }
>
> +bool memory_region_is_logging(MemoryRegion *mr, uint8_t client)
> +{
> + return memory_region_get_dirty_log_mask(mr) & (1 << client);
> +}
> +
> bool memory_region_is_rom(MemoryRegion *mr)
> {
> return mr->ram && mr->readonly;
> diff --git a/xen-hvm.c b/xen-hvm.c
> index 315864c..338ab29 100644
> --- a/xen-hvm.c
> +++ b/xen-hvm.c
> @@ -488,7 +488,7 @@ static void xen_set_memory(struct MemoryListener *listener,
> XenIOState *state = container_of(listener, XenIOState, memory_listener);
> hwaddr start_addr = section->offset_within_address_space;
> ram_addr_t size = int128_get64(section->size);
> - bool log_dirty = memory_region_is_logging(section->mr);
> + bool log_dirty = memory_region_is_logging(section->mr, DIRTY_MEMORY_VGA);
> hvmmem_type_t mem_type;
>
> if (section->mr == &ram_memory) {
> --
> 1.8.3.1
>
>
next prev parent reply other threads:[~2015-05-26 7:46 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 16:28 [Qemu-devel] [PATCH v2 00/29] Dirty bitmap atomic access and optimizations Paolo Bonzini
2015-04-27 16:28 ` [Qemu-devel] [PATCH 01/29] memory: the only dirty memory flag for users is DIRTY_MEMORY_VGA Paolo Bonzini
2015-05-26 7:00 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 02/29] g364fb: remove pointless call to memory_region_set_coalescing Paolo Bonzini
2015-05-26 12:53 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 03/29] display: enable DIRTY_MEMORY_VGA tracking explicitly Paolo Bonzini
2015-05-26 7:13 ` Fam Zheng
2015-05-26 8:14 ` Paolo Bonzini
2015-05-26 11:24 ` Paolo Bonzini
2015-05-26 11:52 ` Peter Maydell
2015-05-26 11:56 ` Paolo Bonzini
2015-05-26 12:08 ` Peter Maydell
2015-05-26 12:10 ` Paolo Bonzini
2015-05-26 12:16 ` Peter Maydell
2015-05-31 20:32 ` Mark Cave-Ayland
2015-04-27 16:28 ` [Qemu-devel] [PATCH 04/29] display: add memory_region_sync_dirty_bitmap calls Paolo Bonzini
2015-05-26 7:36 ` Fam Zheng
2015-05-26 8:14 ` Paolo Bonzini
2015-04-27 16:28 ` [Qemu-devel] [PATCH 05/29] memory: differentiate memory_region_is_logging and memory_region_get_dirty_log_mask Paolo Bonzini
2015-05-26 7:46 ` Fam Zheng [this message]
2015-05-26 11:35 ` Paolo Bonzini
2015-04-27 16:28 ` [Qemu-devel] [PATCH 06/29] memory: prepare for multiple bits in the dirty log mask Paolo Bonzini
2015-05-26 7:55 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 07/29] framebuffer: check memory_region_is_logging Paolo Bonzini
2015-05-26 8:02 ` Fam Zheng
2015-05-26 11:16 ` Paolo Bonzini
2015-04-27 16:28 ` [Qemu-devel] [PATCH 08/29] ui/console: remove dpy_gfx_update_dirty Paolo Bonzini
2015-05-26 8:03 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 09/29] memory: track DIRTY_MEMORY_CODE in mr->dirty_log_mask Paolo Bonzini
2015-05-26 8:06 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 10/29] kvm: accept non-mapped memory in kvm_dirty_pages_log_change Paolo Bonzini
2015-05-26 8:10 ` Fam Zheng
2015-05-26 8:16 ` Paolo Bonzini
2015-05-26 8:22 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 11/29] memory: include DIRTY_MEMORY_MIGRATION in the dirty log mask Paolo Bonzini
2015-05-26 8:40 ` Fam Zheng
2015-05-26 9:07 ` Paolo Bonzini
2015-05-26 9:22 ` Fam Zheng
2015-05-26 9:26 ` Paolo Bonzini
2015-05-26 9:48 ` Fam Zheng
2015-05-26 9:07 ` Paolo Bonzini
2015-04-27 16:28 ` [Qemu-devel] [PATCH 12/29] kvm: remove special handling of " Paolo Bonzini
2015-05-26 8:56 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 13/29] ram_addr: tweaks to xen_modified_memory Paolo Bonzini
2015-05-26 12:52 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 14/29] exec: use memory_region_get_dirty_log_mask to optimize dirty tracking Paolo Bonzini
2015-05-26 10:42 ` Fam Zheng
2015-05-26 10:58 ` Paolo Bonzini
2015-05-26 11:12 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 15/29] exec: move functions to translate-all.h Paolo Bonzini
2015-05-26 10:50 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 16/29] translate-all: remove unnecessary argument to tb_invalidate_phys_range Paolo Bonzini
2015-05-26 10:51 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 17/29] cputlb: remove useless arguments to tlb_unprotect_code_phys, rename Paolo Bonzini
2015-05-26 10:53 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 18/29] translate-all: make less of tb_invalidate_phys_page_range depend on is_cpu_write_access Paolo Bonzini
2015-04-27 16:28 ` [Qemu-devel] [PATCH 19/29] exec: pass client mask to cpu_physical_memory_set_dirty_range Paolo Bonzini
2015-05-26 11:08 ` Fam Zheng
2015-05-26 11:28 ` Paolo Bonzini
2015-04-27 16:28 ` [Qemu-devel] [PATCH 20/29] exec: invert return value of cpu_physical_memory_get_clean, rename Paolo Bonzini
2015-05-26 11:26 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 21/29] exec: only check relevant bitmaps for cleanliness Paolo Bonzini
2015-05-26 11:31 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 22/29] memory: do not touch code dirty bitmap unless TCG is enabled Paolo Bonzini
2015-05-26 11:33 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 23/29] bitmap: add atomic set functions Paolo Bonzini
2015-05-26 11:54 ` Fam Zheng
2015-05-26 11:58 ` Paolo Bonzini
2015-05-26 12:36 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 24/29] bitmap: add atomic test and clear Paolo Bonzini
2015-05-26 12:27 ` Fam Zheng
2015-05-26 12:32 ` Fam Zheng
2015-05-26 12:33 ` Paolo Bonzini
2015-04-27 16:28 ` [Qemu-devel] [PATCH 25/29] memory: use atomic ops for setting dirty memory bits Paolo Bonzini
2015-05-26 12:29 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 26/29] migration: move dirty bitmap sync to ram_addr.h Paolo Bonzini
2015-05-26 12:34 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 27/29] memory: replace cpu_physical_memory_reset_dirty() with test-and-clear Paolo Bonzini
2015-05-26 12:42 ` Fam Zheng
2015-05-26 12:45 ` Paolo Bonzini
2015-04-27 16:28 ` [Qemu-devel] [PATCH 28/29] memory: make cpu_physical_memory_sync_dirty_bitmap() fully atomic Paolo Bonzini
2015-05-26 12:45 ` Fam Zheng
2015-04-27 16:28 ` [Qemu-devel] [PATCH 29/29] memory: strengthen assertions on mr->terminates Paolo Bonzini
2015-05-26 12:49 ` Fam Zheng
2015-05-26 12:52 ` Paolo Bonzini
2015-05-26 12:56 ` Fam Zheng
2015-05-25 21:50 ` [Qemu-devel] [PATCH v2 00/29] Dirty bitmap atomic access and optimizations Paolo Bonzini
2015-05-26 12:58 ` Fam Zheng
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=20150526074634.GF13749@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).