From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
rth@redhat.com, qemu-devel@nongnu.org,
Juan Quintela <quintela@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC 4/6] migration: move dirty bitmap sync to ram_addr.h
Date: Thu, 27 Nov 2014 16:29:06 +0000 [thread overview]
Message-ID: <20141127162905.GG2583@work-vm> (raw)
In-Reply-To: <1417091366-4469-5-git-send-email-stefanha@redhat.com>
* Stefan Hajnoczi (stefanha@redhat.com) wrote:
> The dirty memory bitmap is managed by ram_addr.h and copied to
> migration_bitmap[] periodically during live migration.
>
> Move the code to sync the bitmap to ram_addr.h where related code lives.
Is this sync code going to need to gain a barrier (although I'm not quite
sure which) to ensure it's picked up all changes?
Dave
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> arch_init.c | 46 ++--------------------------------------------
> include/exec/ram_addr.h | 44 ++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 46 insertions(+), 44 deletions(-)
>
> diff --git a/arch_init.c b/arch_init.c
> index 7680d28..79c7784 100644
> --- a/arch_init.c
> +++ b/arch_init.c
> @@ -436,52 +436,10 @@ ram_addr_t migration_bitmap_find_and_reset_dirty(MemoryRegion *mr,
> return (next - base) << TARGET_PAGE_BITS;
> }
>
> -static inline bool migration_bitmap_set_dirty(ram_addr_t addr)
> -{
> - bool ret;
> - int nr = addr >> TARGET_PAGE_BITS;
> -
> - ret = test_and_set_bit(nr, migration_bitmap);
> -
> - if (!ret) {
> - migration_dirty_pages++;
> - }
> - return ret;
> -}
> -
> static void migration_bitmap_sync_range(ram_addr_t start, ram_addr_t length)
> {
> - ram_addr_t addr;
> - unsigned long page = BIT_WORD(start >> TARGET_PAGE_BITS);
> -
> - /* start address is aligned at the start of a word? */
> - if (((page * BITS_PER_LONG) << TARGET_PAGE_BITS) == start) {
> - int k;
> - int nr = BITS_TO_LONGS(length >> TARGET_PAGE_BITS);
> - unsigned long *src = ram_list.dirty_memory[DIRTY_MEMORY_MIGRATION];
> -
> - for (k = page; k < page + nr; k++) {
> - if (src[k]) {
> - unsigned long new_dirty;
> - new_dirty = ~migration_bitmap[k];
> - migration_bitmap[k] |= src[k];
> - new_dirty &= src[k];
> - migration_dirty_pages += ctpopl(new_dirty);
> - src[k] = 0;
> - }
> - }
> - } else {
> - for (addr = 0; addr < length; addr += TARGET_PAGE_SIZE) {
> - if (cpu_physical_memory_get_dirty(start + addr,
> - TARGET_PAGE_SIZE,
> - DIRTY_MEMORY_MIGRATION)) {
> - cpu_physical_memory_reset_dirty(start + addr,
> - TARGET_PAGE_SIZE,
> - DIRTY_MEMORY_MIGRATION);
> - migration_bitmap_set_dirty(start + addr);
> - }
> - }
> - }
> + migration_dirty_pages +=
> + cpu_physical_memory_sync_dirty_bitmap(migration_bitmap, start, length);
> }
>
>
> diff --git a/include/exec/ram_addr.h b/include/exec/ram_addr.h
> index ba90daa..87a8b28 100644
> --- a/include/exec/ram_addr.h
> +++ b/include/exec/ram_addr.h
> @@ -190,5 +190,49 @@ static inline void cpu_physical_memory_clear_dirty_range(ram_addr_t start,
> void cpu_physical_memory_reset_dirty(ram_addr_t start, ram_addr_t length,
> unsigned client);
>
> +static inline
> +uint64_t cpu_physical_memory_sync_dirty_bitmap(unsigned long *dest,
> + ram_addr_t start,
> + ram_addr_t length)
> +{
> + ram_addr_t addr;
> + unsigned long page = BIT_WORD(start >> TARGET_PAGE_BITS);
> + uint64_t num_dirty = 0;
> +
> + /* start address is aligned at the start of a word? */
> + if (((page * BITS_PER_LONG) << TARGET_PAGE_BITS) == start) {
> + int k;
> + int nr = BITS_TO_LONGS(length >> TARGET_PAGE_BITS);
> + unsigned long *src = ram_list.dirty_memory[DIRTY_MEMORY_MIGRATION];
> +
> + for (k = page; k < page + nr; k++) {
> + if (src[k]) {
> + unsigned long new_dirty;
> + new_dirty = ~dest[k];
> + dest[k] |= src[k];
> + new_dirty &= src[k];
> + num_dirty += ctpopl(new_dirty);
> + src[k] = 0;
> + }
> + }
> + } else {
> + for (addr = 0; addr < length; addr += TARGET_PAGE_SIZE) {
> + if (cpu_physical_memory_get_dirty(start + addr,
> + TARGET_PAGE_SIZE,
> + DIRTY_MEMORY_MIGRATION)) {
> + cpu_physical_memory_reset_dirty(start + addr,
> + TARGET_PAGE_SIZE,
> + DIRTY_MEMORY_MIGRATION);
> + long k = (start + addr) >> TARGET_PAGE_BITS;
> + if (!test_and_set_bit(k, dest)) {
> + num_dirty++;
> + }
> + }
> + }
> + }
> +
> + return num_dirty;
> +}
> +
> #endif
> #endif
> --
> 2.1.0
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-11-27 16:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 12:29 [Qemu-devel] [RFC 0/6] memory: make dirty_memory[] accesses atomic Stefan Hajnoczi
2014-11-27 12:29 ` [Qemu-devel] [RFC 1/6] bitmap: add atomic set functions Stefan Hajnoczi
2014-11-27 16:42 ` Paolo Bonzini
2014-12-01 13:52 ` Stefan Hajnoczi
2014-11-27 12:29 ` [Qemu-devel] [RFC 2/6] bitmap: add atomic test and clear Stefan Hajnoczi
2014-11-27 16:43 ` Paolo Bonzini
2014-12-01 13:53 ` Stefan Hajnoczi
2014-11-27 12:29 ` [Qemu-devel] [RFC 3/6] memory: use atomic ops for setting dirty memory bits Stefan Hajnoczi
2014-11-27 12:29 ` [Qemu-devel] [RFC 4/6] migration: move dirty bitmap sync to ram_addr.h Stefan Hajnoczi
2014-11-27 16:29 ` Dr. David Alan Gilbert [this message]
2014-12-01 14:01 ` Stefan Hajnoczi
2014-12-01 14:49 ` Dr. David Alan Gilbert
2014-11-27 12:29 ` [Qemu-devel] [RFC 5/6] memory: replace cpu_physical_memory_reset_dirty() with test-and-clear Stefan Hajnoczi
2014-11-27 12:29 ` [Qemu-devel] [RFC 6/6] memory: make cpu_physical_memory_sync_dirty_bitmap() fully atomic Stefan Hajnoczi
2014-11-27 13:21 ` [Qemu-devel] [RFC 0/6] memory: make dirty_memory[] accesses atomic Peter Maydell
2014-11-28 12:44 ` Stefan Hajnoczi
2015-03-23 11:09 ` Paolo Bonzini
2015-03-24 16:48 ` Stefan Hajnoczi
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=20141127162905.GG2583@work-vm \
--to=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@redhat.com \
--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).