From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
arei.gonglei@huawei.com, peterx@redhat.com
Subject: [Qemu-devel] [PATCH v2 6/7] exec: Factor out section_covers_addr
Date: Tue, 1 Mar 2016 14:18:23 +0800 [thread overview]
Message-ID: <1456813104-25902-7-git-send-email-famz@redhat.com> (raw)
In-Reply-To: <1456813104-25902-1-git-send-email-famz@redhat.com>
This will be shared by the next patch.
Also add a comment explaining the unobvious condition on "size.hi".
Signed-off-by: Fam Zheng <famz@redhat.com>
---
exec.c | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/exec.c b/exec.c
index ad8b826..b4e2eb5 100644
--- a/exec.c
+++ b/exec.c
@@ -307,6 +307,16 @@ static void phys_page_compact_all(AddressSpaceDispatch *d, int nodes_nb)
}
}
+static inline bool section_covers_addr(const MemoryRegionSection *section,
+ hwaddr addr)
+{
+ /* Memory topology clips a memory region to 2^64, size.hi >= 0 means the
+ * section must cover any addr. */
+ return section->size.hi ||
+ range_covers_byte(section->offset_within_address_space,
+ section->size.lo, addr);
+}
+
static MemoryRegionSection *phys_page_find(PhysPageEntry lp, hwaddr addr,
Node *nodes, MemoryRegionSection *sections)
{
@@ -322,9 +332,7 @@ static MemoryRegionSection *phys_page_find(PhysPageEntry lp, hwaddr addr,
lp = p[(index >> (i * P_L2_BITS)) & (P_L2_SIZE - 1)];
}
- if (sections[lp.ptr].size.hi ||
- range_covers_byte(sections[lp.ptr].offset_within_address_space,
- sections[lp.ptr].size.lo, addr)) {
+ if (section_covers_addr(§ions[lp.ptr], addr)) {
return §ions[lp.ptr];
} else {
return §ions[PHYS_SECTION_UNASSIGNED];
--
2.4.3
next prev parent reply other threads:[~2016-03-01 6:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 6:18 [Qemu-devel] [PATCH v2 0/7] memory: Clean up MemoryRegion.ram_addr and optimize address_space_translate Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 1/7] exec: Return RAMBlock pointer from allocating functions Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 2/7] memory: Move assignment to ram_block to memory_region_init_* Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 3/7] memory: Implement memory_region_get_ram_addr with mr->ram_block Fam Zheng
2016-03-01 6:58 ` Gonglei (Arei)
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 4/7] memory: Drop MemoryRegion.ram_addr Fam Zheng
2016-03-07 9:17 ` [Qemu-devel] [PATCH] scripts: Fix dump-guest-memory.py for MemoryRegion.ram_block removal Fam Zheng
2016-03-07 9:37 ` Laszlo Ersek
2016-03-07 9:45 ` Fam Zheng
2016-03-07 10:08 ` Laszlo Ersek
2016-03-07 13:00 ` Paolo Bonzini
2016-03-07 16:35 ` Janosch Frank
2016-03-08 7:54 ` Janosch Frank
2016-03-08 8:54 ` Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 5/7] exec: Pass RAMBlock pointer to qemu_ram_free Fam Zheng
2016-03-01 6:18 ` Fam Zheng [this message]
2016-03-01 7:23 ` [Qemu-devel] [PATCH v2 6/7] exec: Factor out section_covers_addr Peter Xu
2016-03-01 9:42 ` Paolo Bonzini
2016-03-02 2:24 ` Fam Zheng
2016-03-01 6:18 ` [Qemu-devel] [PATCH v2 7/7] exec: Introduce AddressSpaceDispatch.mru_section Fam Zheng
2016-03-01 9:43 ` [Qemu-devel] [PATCH v2 0/7] memory: Clean up MemoryRegion.ram_addr and optimize address_space_translate Paolo Bonzini
2016-03-07 8:53 ` Laszlo Ersek
2016-03-07 9:04 ` Fam Zheng
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=1456813104-25902-7-git-send-email-famz@redhat.com \
--to=famz@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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).