From: Peter Xu <peterx@redhat.com>
To: Chuang Xu <xuchuangxclwt@bytedance.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, quintela@redhat.com,
pbonzini@redhat.com, david@redhat.com, philmd@linaro.org,
zhouyibo@bytedance.com
Subject: Re: [RFC v5 0/3] migration: reduce time of loading non-iterable vmstate
Date: Tue, 17 Jan 2023 10:41:51 -0500 [thread overview]
Message-ID: <Y8bBv1xQZ1pm8TDZ@x1n> (raw)
In-Reply-To: <20230117115511.3215273-1-xuchuangxclwt@bytedance.com>
On Tue, Jan 17, 2023 at 07:55:08PM +0800, Chuang Xu wrote:
> In this version:
>
> - rename rcu_read_locked() to rcu_read_is_locked().
> - adjust the sanity check in address_space_to_flatview().
> - improve some comments.
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2023-01-17 15:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 11:55 [RFC v5 0/3] migration: reduce time of loading non-iterable vmstate Chuang Xu
2023-01-17 11:55 ` [RFC v5 1/3] rcu: introduce rcu_read_is_locked() Chuang Xu
2023-02-02 10:59 ` Juan Quintela
2023-02-14 7:57 ` Chuang Xu
2023-01-17 11:55 ` [RFC v5 2/3] memory: add depth assert in address_space_to_flatview Chuang Xu
2023-02-08 19:31 ` Juan Quintela
2023-01-17 11:55 ` [RFC v5 3/3] migration: reduce time of loading non-iterable vmstate Chuang Xu
2023-02-02 11:01 ` Juan Quintela
2023-01-17 15:41 ` Peter Xu [this message]
2023-02-02 11:07 ` [RFC v5 0/3] " Juan Quintela
2023-02-15 17:00 ` Juan Quintela
2023-02-15 17:06 ` Claudio Fontana
2023-02-15 19:10 ` Juan Quintela
2023-02-16 15:41 ` Chuang Xu
[not found] ` <a555b989-27be-006e-0d00-9f1688c5be4e@bytedance.com>
2023-02-17 8:11 ` Chuang Xu
2023-02-17 15:52 ` Peter Xu
2023-02-20 13:36 ` Chuang Xu
2023-02-21 3:38 ` Chuang Xu
2023-02-21 8:57 ` Chuang Xu
2023-02-21 20:36 ` Peter Xu
2023-02-22 6:27 ` Chuang Xu
2023-02-22 15:57 ` Peter Xu
2023-02-23 3:28 ` Chuang Xu
2023-02-25 15:32 ` Peter Xu
2023-02-27 13:19 ` Chuang Xu
2023-02-27 20:56 ` Peter Xu
2023-02-20 9:53 ` Chuang Xu
2023-02-20 12:07 ` Juan Quintela
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=Y8bBv1xQZ1pm8TDZ@x1n \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=xuchuangxclwt@bytedance.com \
--cc=zhouyibo@bytedance.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).