qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v3 0/3] vfio: fixes for better support for 128 b


From: Alexey Kardashevskiy
Subject: Re: [Qemu-devel] [PATCH v3 0/3] vfio: fixes for better support for 128 bit memory section sizes
Date: Tue, 10 Sep 2013 14:23:13 +1000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8

On 08/29/2013 12:29 AM, Paolo Bonzini wrote:
> 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. :)


Soooo, Alex, can I consider them (first two I guess) taken by you to your
tree? I cannot find them in any tree...


-- 
Alexey



reply via email to

[Prev in Thread] Current Thread [Next in Thread]