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: Thu, 22 Aug 2013 07:36:46 +0200 [thread overview]
Message-ID: <5215A36E.8090609@redhat.com> (raw)
In-Reply-To: <52157127.3010504@ozlabs.ru>
Il 22/08/2013 04:02, Alexey Kardashevskiy ha scritto:
>> 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
>
> Like this? I am really scared to screw here :)
>
> static inline Int128 int128_exts64(int64_t a)
> {
> return (Int128) { .lo = a, .hi = (a < 0) ? -1 : 0 };
> }
Yes, or just a >> 63.
>> - use int128_neg(int128_make64(TARGET_PAGE_SIZE)) or something like that
>
> Did you actually mean TARGET_PAGE_SIZE-1 (with -1)? I'll better use this
> for now.
it would be either ~(TARGET_PAGE_SIZE-1) or -TARGET_PAGE_SIZE, I think.
>> - add a new int128_make function that takes a low/high pair and use
>> int128_make(TARGET_PAGE_MASK, -1)
>
> I liked this one actually but you called it "worst" :)
It is really the same as #1 but inlined, which is why I called it the worst.
#2 is ugly for a different reason, namely because it changes the code
more substantially, from using TARGET_PAGE_MASK pre-patch to
TARGET_PAGE_SIZE post-patch.
Paolo
prev parent reply other threads:[~2013-08-22 5:37 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
2013-08-22 2:02 ` Alexey Kardashevskiy
2013-08-22 5:36 ` Paolo Bonzini [this message]
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=5215A36E.8090609@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 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).