Peter Maydell writes:
> On 22 October 2012 10:35, Avi Kivity wrote:
>> On 10/15/2012 03:16 PM, Avi Kivity wrote:
>>> Rebased tree in the same place:
>>>
>>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/dma
>>>
>>
>> Anthony, or Blue, can you pull please? The neighbours are starti
On 22 October 2012 10:35, Avi Kivity wrote:
> On 10/15/2012 03:16 PM, Avi Kivity wrote:
>> Rebased tree in the same place:
>>
>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/dma
>>
>
> Anthony, or Blue, can you pull please? The neighbours are starting to
> complain about the smell.
On 10/15/2012 03:16 PM, Avi Kivity wrote:
> On 10/11/2012 11:01 PM, Anthony Liguori wrote:
>> This conflicts with a recent pull from Stefano in xen-all.c. The
>> difference doesn't look that awful but since I don't have a xen test
>> setup, I'm not confident in resolving it myself.
>>
>> Can you
On 10/11/2012 11:01 PM, Anthony Liguori wrote:
> This conflicts with a recent pull from Stefano in xen-all.c. The
> difference doesn't look that awful but since I don't have a xen test
> setup, I'm not confident in resolving it myself.
>
> Can you rebase and fixup?
>
Rebased tree in the same pl
Avi Kivity writes:
> Most of the work on the memory API focused on memory access targets - the
> memory regions
> and how they are composed into an address space. This patchset tackles the
> initator
> side of the question - how to originate accesses.
>
> The AddressSpace object, is exported t
Most of the work on the memory API focused on memory access targets - the
memory regions
and how they are composed into an address space. This patchset tackles the
initator
side of the question - how to originate accesses.
The AddressSpace object, is exported to users and becomes the representa
