On 18/02/2013 09:59, Andreas Färber wrote:
Am 18.02.2013 09:53, schrieb KONRAD Frédéric:
On 18/02/2013 09:47, Andreas Färber wrote:
Am 12.02.2013 18:00, schrieb fred.kon...@greensocs.com:
From: KONRAD Frederic
These structures must be made public to avoid two memory allocations for
refactore
Am 18.02.2013 09:53, schrieb KONRAD Frédéric:
> On 18/02/2013 09:47, Andreas Färber wrote:
>> Am 12.02.2013 18:00, schrieb fred.kon...@greensocs.com:
>>> From: KONRAD Frederic
>>>
>>> These structures must be made public to avoid two memory allocations for
>>> refactored virtio devices.
>>>
>>> Ch
On 18/02/2013 09:47, Andreas Färber wrote:
Am 12.02.2013 18:00, schrieb fred.kon...@greensocs.com:
From: KONRAD Frederic
These structures must be made public to avoid two memory allocations for
refactored virtio devices.
Changes V2 <- V1:
* Move the dataplane include into the header (vir
Am 12.02.2013 18:00, schrieb fred.kon...@greensocs.com:
> From: KONRAD Frederic
>
> These structures must be made public to avoid two memory allocations for
> refactored virtio devices.
>
> Changes V2 <- V1:
> * Move the dataplane include into the header (virtio-blk).
>
> Signed-off-by: KON
Is this ok for everybody?
On 12/02/2013 18:00, fred.kon...@greensocs.com wrote:
From: KONRAD Frederic
These structures must be made public to avoid two memory allocations for
refactored virtio devices.
Changes V2 <- V1:
* Move the dataplane include into the header (virtio-blk).
Signed-o
From: KONRAD Frederic
These structures must be made public to avoid two memory allocations for
refactored virtio devices.
Changes V2 <- V1:
* Move the dataplane include into the header (virtio-blk).
Signed-off-by: KONRAD Frederic
---
hw/virtio-balloon.c| 15 ---
hw/virtio-
