Re: [PATCH v1] virtio-mem: add memory via add_memory_driver_managed()

2020-06-11 Thread Michael S. Tsirkin
On Thu, Jun 11, 2020 at 01:33:04PM +0200, David Hildenbrand wrote: > > > Am 11.06.2020 um 13:18 schrieb Michael S. Tsirkin : > > > On Thu, Jun 11, 2020 at 01:00:24PM +0200, David Hildenbrand wrote: > > I'd like to have this patch in 5.8, with the initial merge of >

Re: [PATCH v1] virtio-mem: add memory via add_memory_driver_managed()

2020-06-11 Thread Michael S. Tsirkin
On Thu, Jun 11, 2020 at 01:00:24PM +0200, David Hildenbrand wrote: > >> I'd like to have this patch in 5.8, with the initial merge of virtio-mem > >> if possible (so the user space representation of virtio-mem added memory > >> resources won't change anymore). > > > > So my plan is to rebase on to

Re: [PATCH v1] virtio-mem: add memory via add_memory_driver_managed()

2020-06-11 Thread David Hildenbrand
>> I'd like to have this patch in 5.8, with the initial merge of virtio-mem >> if possible (so the user space representation of virtio-mem added memory >> resources won't change anymore). > > So my plan is to rebase on top of -rc1 and merge this for rc2 then. > I don't like rebase on top of tip as

Re: [PATCH v1] virtio-mem: add memory via add_memory_driver_managed()

2020-06-11 Thread David Hildenbrand
On 11.06.20 12:32, Pankaj Gupta wrote: >> Virtio-mem managed memory is always detected and added by the virtio-mem >> driver, never using something like the firmware-provided memory map. >> This is the case after an ordinary system reboot, and has to be guaranteed >> after kexec. Especially, virtio

Re: [PATCH v1] virtio-mem: add memory via add_memory_driver_managed()

2020-06-11 Thread Pankaj Gupta
> Virtio-mem managed memory is always detected and added by the virtio-mem > driver, never using something like the firmware-provided memory map. > This is the case after an ordinary system reboot, and has to be guaranteed > after kexec. Especially, virtio-mem added memory resources can contain > i

Re: [PATCH v1] virtio-mem: add memory via add_memory_driver_managed()

2020-06-11 Thread Michael S. Tsirkin
virtio-mem: add memory via add_memory_driver_managed() On Thu, Jun 11, 2020 at 11:35:18AM +0200, David Hildenbrand wrote: > Virtio-mem managed memory is always detected and added by the virtio-mem > driver, never using something like the firmware-provided memory map. > This is the case after an o

[PATCH v1] virtio-mem: add memory via add_memory_driver_managed()

2020-06-11 Thread David Hildenbrand
Virtio-mem managed memory is always detected and added by the virtio-mem driver, never using something like the firmware-provided memory map. This is the case after an ordinary system reboot, and has to be guaranteed after kexec. Especially, virtio-mem added memory resources can contain inaccessibl