From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: David Gibson <david@gibson.dropbear.id.au>,
Paolo Bonzini <pbonzini@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
peterx@redhat.com, Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PATCH 2/4] exec: rename resolve_subpage
Date: Mon, 15 May 2017 16:50:58 +0800 [thread overview]
Message-ID: <1494838260-30439-3-git-send-email-peterx@redhat.com> (raw)
In-Reply-To: <1494838260-30439-1-git-send-email-peterx@redhat.com>
It is not easy for people to know "what this parameter does" before
knowing "what is subpage". Let's use "is_mmio" to make it easier to
understand.
Signed-off-by: Peter Xu <peterx@redhat.com>
---
exec.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/exec.c b/exec.c
index 1d76c63..0adae94 100644
--- a/exec.c
+++ b/exec.c
@@ -403,7 +403,7 @@ bool memory_region_is_unassigned(MemoryRegion *mr)
/* Called from RCU critical section */
static MemoryRegionSection *address_space_lookup_region(AddressSpaceDispatch *d,
hwaddr addr,
- bool resolve_subpage)
+ bool is_mmio)
{
MemoryRegionSection *section = atomic_read(&d->mru_section);
subpage_t *subpage;
@@ -416,7 +416,7 @@ static MemoryRegionSection *address_space_lookup_region(AddressSpaceDispatch *d,
section = phys_page_find(d, addr);
update = true;
}
- if (resolve_subpage && section->mr->subpage) {
+ if (is_mmio && section->mr->subpage) {
subpage = container_of(section->mr, subpage_t, iomem);
section = &d->map.sections[subpage->sub_section[SUBPAGE_IDX(addr)]];
}
@@ -429,13 +429,13 @@ static MemoryRegionSection *address_space_lookup_region(AddressSpaceDispatch *d,
/* Called from RCU critical section */
static MemoryRegionSection *
address_space_translate_internal(AddressSpaceDispatch *d, hwaddr addr, hwaddr *xlat,
- hwaddr *plen, bool resolve_subpage)
+ hwaddr *plen, bool is_mmio)
{
MemoryRegionSection *section;
MemoryRegion *mr;
Int128 diff;
- section = address_space_lookup_region(d, addr, resolve_subpage);
+ section = address_space_lookup_region(d, addr, is_mmio);
/* Compute offset within MemoryRegionSection */
addr -= section->offset_within_address_space;
--
2.7.4
next prev parent reply other threads:[~2017-05-15 8:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 8:50 [Qemu-devel] [PATCH 0/4] exec: address space translation cleanups Peter Xu
2017-05-15 8:50 ` [Qemu-devel] [PATCH 1/4] exec: simplify phys_page_find() params Peter Xu
2017-05-16 2:53 ` David Gibson
2017-05-16 10:02 ` Paolo Bonzini
2017-05-15 8:50 ` Peter Xu [this message]
2017-05-15 9:03 ` [Qemu-devel] [PATCH 2/4] exec: rename resolve_subpage Paolo Bonzini
2017-05-15 12:16 ` Peter Xu
2017-05-15 8:50 ` [Qemu-devel] [PATCH 3/4] exec: further use is_mmio Peter Xu
2017-05-15 9:04 ` Paolo Bonzini
2017-05-15 9:29 ` Peter Xu
2017-05-15 8:51 ` [Qemu-devel] [PATCH 4/4] exec: abstract address_space_do_translate() Peter Xu
2017-05-16 13:24 ` [Qemu-devel] [PATCH 0/4] exec: address space translation cleanups Maxime Coquelin
2017-05-16 16:51 ` Maxime Coquelin
2017-05-16 16:54 ` Paolo Bonzini
2017-05-16 17:01 ` Maxime Coquelin
2017-05-17 4:23 ` Peter Xu
2017-05-17 5:57 ` Peter Xu
2017-05-17 7:17 ` Maxime Coquelin
2017-05-17 7:26 ` Paolo Bonzini
2017-05-17 8:38 ` Peter 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=1494838260-30439-3-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).