From: Peter Xu <peterx@redhat.com>
To: Gavin Shan <gshan@redhat.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, pbonzini@redhat.com,
peter.maydell@linaro.org, david@redhat.com, philmd@linaro.org,
mst@redhat.com, cohuck@redhat.com, quintela@redhat.com,
dgilbert@redhat.com, maz@kernel.org, zhenyzha@redhat.com,
shan.gavin@gmail.com
Subject: Re: [PATCH v1 2/6] migration: Add last stage indicator to global dirty log synchronization
Date: Tue, 21 Feb 2023 12:36:53 -0500 [thread overview]
Message-ID: <Y/UBNX7ljyTYLa6H@x1n> (raw)
In-Reply-To: <20230213003925.40158-3-gshan@redhat.com>
On Mon, Feb 13, 2023 at 08:39:21AM +0800, Gavin Shan wrote:
> The global dirty log synchronization is used when KVM and dirty ring
> are enabled. There is a particularity for ARM64 where the backup
> bitmap is used to track dirty pages in non-running-vcpu situations.
> It means the dirty ring works with the combination of ring buffer
> and backup bitmap. The dirty bits in the backup bitmap needs to
> collected in the last stage of live migration.
>
> In order to identify the last stage of live migration and pass it
> down, an extra parameter is added to the relevant functions and
> callbacks. This last stage indicator isn't used until the dirty
> ring is enabled in the subsequent patches.
>
> No functional change intended.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
One trivial thing to mention below.
> ---
> accel/kvm/kvm-all.c | 2 +-
> include/exec/memory.h | 5 +++--
> migration/dirtyrate.c | 4 ++--
> migration/ram.c | 20 ++++++++++----------
> softmmu/memory.c | 10 +++++-----
> 5 files changed, 21 insertions(+), 20 deletions(-)
>
> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
> index 9b26582655..01a6a026af 100644
> --- a/accel/kvm/kvm-all.c
> +++ b/accel/kvm/kvm-all.c
> @@ -1554,7 +1554,7 @@ static void kvm_log_sync(MemoryListener *listener,
> kvm_slots_unlock();
> }
>
> -static void kvm_log_sync_global(MemoryListener *l)
> +static void kvm_log_sync_global(MemoryListener *l, bool last_stage)
> {
> KVMMemoryListener *kml = container_of(l, KVMMemoryListener, listener);
> KVMState *s = kvm_state;
> diff --git a/include/exec/memory.h b/include/exec/memory.h
> index 2e602a2fad..75b2fd9f48 100644
> --- a/include/exec/memory.h
> +++ b/include/exec/memory.h
> @@ -929,8 +929,9 @@ struct MemoryListener {
> * its @log_sync must be NULL. Vice versa.
> *
> * @listener: The #MemoryListener.
> + * @last_stage: The last stage to synchronize the log during migration
IMHO it may be important to mention the vcpu status here that the caller
guarantees to call the last_stage==true only once, only after all vcpus are
stopped (and vcpus will not be started again if migration succeeded).
> */
> - void (*log_sync_global)(MemoryListener *listener);
> + void (*log_sync_global)(MemoryListener *listener, bool last_stage);
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2023-02-21 17:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 0:39 [PATCH v1 0/6] hw/arm/virt: Support dirty ring Gavin Shan
2023-02-13 0:39 ` [PATCH v1 1/6] linux-headers: Update for " Gavin Shan
2023-02-21 16:30 ` Peter Maydell
2023-02-21 23:18 ` Gavin Shan
2023-02-22 8:49 ` Cornelia Huck
2023-02-22 9:03 ` Gavin Shan
2023-02-13 0:39 ` [PATCH v1 2/6] migration: Add last stage indicator to global dirty log synchronization Gavin Shan
2023-02-21 17:36 ` Peter Xu [this message]
2023-02-21 23:20 ` Gavin Shan
2023-02-13 0:39 ` [PATCH v1 3/6] kvm: Synchronize the backup bitmap in the last stage Gavin Shan
2023-02-21 17:46 ` Peter Xu
2023-02-21 23:44 ` Gavin Shan
2023-02-21 23:58 ` Peter Xu
2023-02-22 6:06 ` Gavin Shan
2023-02-13 0:39 ` [PATCH v1 4/6] kvm: Add helper kvm_dirty_ring_init() Gavin Shan
2023-02-21 20:12 ` Peter Xu
2023-02-13 0:39 ` [PATCH v1 5/6] hw/arm/virt: Enable backup bitmap for dirty ring Gavin Shan
2023-02-21 16:27 ` Peter Maydell
2023-02-22 4:35 ` Gavin Shan
2023-02-22 15:54 ` Peter Maydell
2023-02-23 0:52 ` Gavin Shan
2023-02-23 11:51 ` Peter Maydell
2023-02-24 10:19 ` Gavin Shan
2023-02-13 0:39 ` [PATCH v1 6/6] kvm: Enable dirty ring for arm64 Gavin Shan
2023-02-17 1:59 ` [PATCH v1 0/6] hw/arm/virt: Support dirty ring Zhenyu Zhang
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=Y/UBNX7ljyTYLa6H@x1n \
--to=peterx@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=gshan@redhat.com \
--cc=maz@kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=shan.gavin@gmail.com \
--cc=zhenyzha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.