From: Chuang Xu <xuchuangxclwt@bytedance.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: dgilbert@redhat.com, quintela@redhat.com, pbonzini@redhat.com,
peterx@redhat.com, david@redhat.com, zhouyibo@bytedance.com
Subject: Re: [External] Re: [RFC v4 2/3] memory: add depth assert in address_space_to_flatview
Date: Wed, 4 Jan 2023 01:39:17 -0600 [thread overview]
Message-ID: <CALophuvab5qa-7nNhz449rowBufsfrAVXqjnRGCn7AZsDAEsrg@mail.gmail.com> (raw)
In-Reply-To: <4db15db9-2f00-c71e-c5e1-e41c81090ee2@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On 2022/12/28 下午6:50, Philippe Mathieu-Daudé wrote:
On 23/12/22 15:23, Chuang Xu wrote:
Before using any flatview, sanity check we're not during a memory
region transaction or the map can be invalid.
Signed-off-by: Chuang Xu <xuchuangxclwt@bytedance.com>
<xuchuangxclwt@bytedance.com>
---
include/exec/memory.h | 9 +++++++++
softmmu/memory.c | 5 +++++
2 files changed, 14 insertions(+)
diff --git a/include/exec/memory.h b/include/exec/memory.h
index 91f8a2395a..66c43b4862 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -1069,8 +1069,17 @@ struct FlatView {
MemoryRegion *root;
};
+int memory_region_transaction_get_depth(void);
Do we want to expose this; isn't the depth internal?
If we need to expose something, can we restrict it to
bool memory_region_in_transaction(void) or
bool memory_region_transaction_in_progress(void)?
Yes, we'd better not expose the value of an internal
variable. I'll make changes in v5.
Thanks!
[-- Attachment #2: Type: text/html, Size: 2032 bytes --]
next prev parent reply other threads:[~2023-01-04 7:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 14:23 [RFC v4 0/3] migration: reduce time of loading non-iterable vmstate Chuang Xu
2022-12-23 14:23 ` [RFC v4 1/3] rcu: introduce rcu_read_locked() Chuang Xu
2023-01-04 14:20 ` Alex Bennée
2023-01-05 8:17 ` Chuang Xu
2022-12-23 14:23 ` [RFC v4 2/3] memory: add depth assert in address_space_to_flatview Chuang Xu
2022-12-23 15:37 ` Peter Xu
2022-12-23 15:47 ` Paolo Bonzini
2022-12-23 15:54 ` Peter Xu
2022-12-28 8:27 ` Paolo Bonzini
2023-01-03 17:43 ` Peter Xu
2023-01-10 8:09 ` Chuang Xu
2023-01-10 14:45 ` Peter Xu
2023-01-12 7:59 ` Chuang Xu
2023-01-12 15:13 ` Peter Xu
2023-01-13 19:29 ` Chuang Xu
2022-12-28 10:50 ` Philippe Mathieu-Daudé
2023-01-04 7:39 ` Chuang Xu [this message]
2022-12-23 14:23 ` [RFC v4 3/3] migration: reduce time of loading non-iterable vmstate Chuang Xu
2022-12-23 16:06 ` David Hildenbrand
2023-01-04 7:31 ` Chuang Xu
2022-12-23 15:50 ` [RFC v4 0/3] " Peter Xu
2022-12-23 19:11 ` Chuang Xu
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=CALophuvab5qa-7nNhz449rowBufsfrAVXqjnRGCn7AZsDAEsrg@mail.gmail.com \
--to=xuchuangxclwt@bytedance.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).