qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/3] vfio: fixes for better support for 128 bit memory section sizes
Date: Wed, 28 Aug 2013 16:29:14 +0200	[thread overview]
Message-ID: <521E093A.6010605@redhat.com> (raw)
In-Reply-To: <1377699047.10408.55.camel@ul30vt.home>

Il 28/08/2013 16:10, Alex Williamson ha scritto:
> On Wed, 2013-08-28 at 13:09 +0200, Paolo Bonzini wrote:
>> Il 28/08/2013 11:46, Alexey Kardashevskiy ha scritto:
>>> On 08/22/2013 09:29 PM, Alexey Kardashevskiy wrote:
>>>> I made a couple of small patches while debugging VFIO on SPAPR
>>>> which uses IOMMU MemoryRegion 2^64 bytes long.
>>>>
>>>> Changes:
>>>> v3:
>>>> * "int128: add int128_exts64()" updated
>>>>
>>>> v2:
>>>> * added int128_exts64() function as a separate patch and used in
>>>> "vfio: Fix 128 bit handling"
>>>>
>>>>
>>>>
>>>> Alexey Kardashevskiy (3):
>>>>   int128: add int128_exts64()
>>>>   vfio: Fix debug output for int128 values
>>>>   vfio: Fix 128 bit handling
>>>>
>>>>  hw/misc/vfio.c        | 19 +++++++++++++------
>>>>  include/qemu/int128.h |  5 +++++
>>>>  2 files changed, 18 insertions(+), 6 deletions(-)
>>>
>>> Ping? I fixed everything I was told to, is there anything left? Or we need
>>> to decide through which tree this should go? :) Thanks!
>>
>> I think it should go through Alex's tree, but he may be busy due to the
>> impending opening of the Linux merge window.
> 
> I can take it if you could ACK the first patch.  Thanks,

Sure, consider it acked. :)

Paolo

  reply	other threads:[~2013-08-28 14:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 11:29 [Qemu-devel] [PATCH v3 0/3] vfio: fixes for better support for 128 bit memory section sizes Alexey Kardashevskiy
2013-08-22 11:29 ` [Qemu-devel] [PATCH v3 1/3] int128: add int128_exts64() Alexey Kardashevskiy
2013-08-22 11:29 ` [Qemu-devel] [PATCH v3 2/3] vfio: Fix debug output for int128 values Alexey Kardashevskiy
2013-08-22 11:29 ` [Qemu-devel] [PATCH v3 3/3] vfio: Fix 128 bit handling Alexey Kardashevskiy
2013-08-28 15:18   ` Alex Williamson
2013-08-29  1:03     ` Alexey Kardashevskiy
2013-08-29  1:42       ` Alex Williamson
2013-08-29  2:26         ` Alexey Kardashevskiy
2013-08-29  6:29           ` Paolo Bonzini
2013-08-29  6:58             ` Alexey Kardashevskiy
2013-08-29  8:50               ` Paolo Bonzini
2013-08-30  6:15                 ` Alexey Kardashevskiy
2013-08-30  6:39                   ` Paolo Bonzini
2013-08-30  6:42                     ` Alexey Kardashevskiy
2013-08-28  9:46 ` [Qemu-devel] [PATCH v3 0/3] vfio: fixes for better support for 128 bit memory section sizes Alexey Kardashevskiy
2013-08-28 11:09   ` Paolo Bonzini
2013-08-28 14:10     ` Alex Williamson
2013-08-28 14:29       ` Paolo Bonzini [this message]
2013-09-10  4:23         ` Alexey Kardashevskiy
2013-09-10  6:51           ` 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=521E093A.6010605@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).