From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
peterx@redhat.com
Subject: [Qemu-devel] [PATCH v2] exec: fix address_space_get_iotlb_entry page mask
Date: Mon, 29 May 2017 12:02:25 +0800 [thread overview]
Message-ID: <1496030545-8719-1-git-send-email-peterx@redhat.com> (raw)
The IOTLB that it returned didn't guarantee that page_mask is indeed a
so-called page mask. That won't affect current usage since now only
vhost is using it (vhost API allows arbitary IOTLB range). However we
have IOTLB scemantic and we should best follow it. This patch fixes this
issue to make sure the page_mask is always a valid page mask.
Fixes: a764040 ("exec: abstract address_space_do_translate()")
Signed-off-by: Peter Xu <peterx@redhat.com>
---
Sorry please use this one. The codes is merely the same, just avoided
moving the codes around unnecessarily.
---
exec.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/exec.c b/exec.c
index ff16f04..3db247c 100644
--- a/exec.c
+++ b/exec.c
@@ -529,16 +529,14 @@ IOMMUTLBEntry address_space_get_iotlb_entry(AddressSpace *as, hwaddr addr,
section.offset_within_region;
if (plen == (hwaddr)-1) {
- /*
- * We use default page size here. Logically it only happens
- * for identity mappings.
- */
- plen = TARGET_PAGE_SIZE;
+ /* If not specified during translation, use default mask */
+ plen = TARGET_PAGE_MASK;
+ } else {
+ /* Make it a valid page mask */
+ assert(plen);
+ plen = (1ULL << (63 - clz64(plen))) - 1;
}
- /* Convert to address mask */
- plen -= 1;
-
return (IOMMUTLBEntry) {
.target_as = section.address_space,
.iova = addr & ~plen,
--
2.7.4
next reply other threads:[~2017-05-29 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 4:02 Peter Xu [this message]
2017-05-30 16:23 ` [Qemu-devel] [PATCH v2] exec: fix address_space_get_iotlb_entry page mask Paolo Bonzini
2017-05-31 6:23 ` 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=1496030545-8719-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=maxime.coquelin@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).