Re: [PATCH v2 05/13] conf: Introduce virtio-mem model

2021-02-22 Thread David Hildenbrand
On 22.02.21 17:28, Peter Krempa wrote: On Mon, Feb 22, 2021 at 16:57:11 +0100, David Hildenbrand wrote: On 22.02.21 16:46, Michal Privoznik wrote: On 2/18/21 4:00 PM, David Hildenbrand wrote: On 18.02.21 14:31, Michal Privoznik wrote: [...] In QEMU, we could make "info balloon" etc. also

Re: [PATCH v2 05/13] conf: Introduce virtio-mem model

2021-02-22 Thread Peter Krempa
On Mon, Feb 22, 2021 at 16:57:11 +0100, David Hildenbrand wrote: > On 22.02.21 16:46, Michal Privoznik wrote: > > On 2/18/21 4:00 PM, David Hildenbrand wrote: > > > On 18.02.21 14:31, Michal Privoznik wrote: [...] > In QEMU, we could make "info balloon" etc. also include virtio-mem provided >

Re: [PATCH v2 05/13] conf: Introduce virtio-mem model

2021-02-22 Thread David Hildenbrand
On 22.02.21 16:46, Michal Privoznik wrote: On 2/18/21 4:00 PM, David Hildenbrand wrote: On 18.02.21 14:31, Michal Privoznik wrote: Since now we have (possibly) two or more devices that allow memory inflation/deflation and accounting for all of them (and thus keeping updated) might be hard.

Re: [PATCH v2 05/13] conf: Introduce virtio-mem model

2021-02-22 Thread Daniel P . Berrangé
On Thu, Feb 18, 2021 at 04:00:05PM +0100, David Hildenbrand wrote: > On 18.02.21 14:31, Michal Privoznik wrote: > > The virtio-mem is paravirtualized mechanism of adding/removing > > memory to/from a VM. A virtio-mem-pci device is split into blocks > > of equal size which are then exposed (all or

Re: [PATCH v2 05/13] conf: Introduce virtio-mem model

2021-02-22 Thread Michal Privoznik
On 2/18/21 4:00 PM, David Hildenbrand wrote: On 18.02.21 14:31, Michal Privoznik wrote: Since now we have (possibly) two or more devices that allow memory inflation/deflation and accounting for all of them (and thus keeping updated) might be hard. Therefore, I'm deliberately forbidding

Re: [PATCH v2 05/13] conf: Introduce virtio-mem model

2021-02-18 Thread Peter Krempa
On Thu, Feb 18, 2021 at 14:31:00 +0100, Michal Privoznik wrote: > The virtio-mem is paravirtualized mechanism of adding/removing > memory to/from a VM. A virtio-mem-pci device is split into blocks > of equal size which are then exposed (all or only a requested > portion of them) to the guest

Re: [PATCH v2 05/13] conf: Introduce virtio-mem model

2021-02-18 Thread David Hildenbrand
On 18.02.21 14:31, Michal Privoznik wrote: The virtio-mem is paravirtualized mechanism of adding/removing memory to/from a VM. A virtio-mem-pci device is split into blocks of equal size which are then exposed (all or only a requested portion of them) to the guest kernel to use as regular memory.

[PATCH v2 05/13] conf: Introduce virtio-mem model

2021-02-18 Thread Michal Privoznik
The virtio-mem is paravirtualized mechanism of adding/removing memory to/from a VM. A virtio-mem-pci device is split into blocks of equal size which are then exposed (all or only a requested portion of them) to the guest kernel to use as regular memory. Therefore, the device has two important

[PATCH v2 05/13] conf: Introduce virtio-mem model

2021-02-09 Thread Michal Privoznik
The virtio-mem is paravirtualized mechanism of adding/removing memory to/from a VM. A virtio-mem-pci device is split into blocks of equal size which are then exposed (all or only a requested portion of them) to the guest kernel to use as regular memory. Therefore, the device has two important