From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 2/2] vfio: Fix 128 bit handling
Date: Wed, 21 Aug 2013 12:07:55 +0200 [thread overview]
Message-ID: <5214917B.4040607@redhat.com> (raw)
In-Reply-To: <1377077318-12966-3-git-send-email-aik@ozlabs.ru>
Il 21/08/2013 11:28, Alexey Kardashevskiy ha scritto:
> Upcoming VFIO on SPAPR PPC64 support will initialize the IOMMU
> memory region with UINT64_MAX (2^64 bytes) size so int128_get64()
> will assert.
>
> The patch takes care of this check. The existing type1 IOMMU code
> is not expected to map all 64 bits of RAM so the patch does not
> touch that part.
>
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> ---
> hw/misc/vfio.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/hw/misc/vfio.c b/hw/misc/vfio.c
> index e917f03..1889225 100644
> --- a/hw/misc/vfio.c
> +++ b/hw/misc/vfio.c
> @@ -1920,6 +1920,7 @@ static void vfio_listener_region_add(MemoryListener *listener,
> VFIOContainer *container = container_of(listener, VFIOContainer,
> iommu_data.listener);
> hwaddr iova, end;
> + Int128 llend;
> void *vaddr;
> int ret;
>
> @@ -1940,13 +1941,17 @@ static void vfio_listener_region_add(MemoryListener *listener,
> }
>
> iova = TARGET_PAGE_ALIGN(section->offset_within_address_space);
> - end = (section->offset_within_address_space + int128_get64(section->size)) &
> - TARGET_PAGE_MASK;
> + llend = int128_make64(section->offset_within_address_space);
> + int128_addto(&llend, section->size);
Please use int128_add.
> + llend.lo &= TARGET_PAGE_MASK;
Int128 is opaque, please use int128_and. To build the constant you have
three choices (from my preferred to IMHO worst):
- add a new int128_exts64 function that sign-extends an int64_t
- use int128_neg(int128_make64(TARGET_PAGE_SIZE)) or something like that
- add a new int128_make function that takes a low/high pair and use
int128_make(TARGET_PAGE_MASK, -1)
Otherwise looks good!
Paolo
>
> - if (iova >= end) {
> + if (int128_ge(int128_make64(iova), llend)) {
> return;
> }
>
> + end = (section->offset_within_address_space + int128_get64(section->size)) &
> + TARGET_PAGE_MASK;
> +
> vaddr = memory_region_get_ram_ptr(section->mr) +
> section->offset_within_region +
> (iova - section->offset_within_address_space);
>
next prev parent reply other threads:[~2013-08-21 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 9:28 [Qemu-devel] [PATCH 0/2] vfio: fixes for better support for 128 bit memory section sizes Alexey Kardashevskiy
2013-08-21 9:28 ` [Qemu-devel] [PATCH 1/2] vfio: Fix debug output for int128 values Alexey Kardashevskiy
2013-08-21 9:28 ` [Qemu-devel] [PATCH 2/2] vfio: Fix 128 bit handling Alexey Kardashevskiy
2013-08-21 10:07 ` Paolo Bonzini [this message]
2013-08-22 2:02 ` Alexey Kardashevskiy
2013-08-22 5:36 ` Paolo Bonzini
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=5214917B.4040607@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.