Messages in this thread | | | Subject | Re: [PATCH v1] virtio-mem: add memory via add_memory_driver_managed() | From | David Hildenbrand <> | Date | Thu, 11 Jun 2020 12:57:25 +0200 |
| |
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-mem added memory resources can contain >> inaccessible parts ("unblocked memory blocks"), blindly forwarding them >> to a kexec kernel is dangerous, as unplugged memory will get accessed >> (esp. written). >> >> Let's use the new way of adding special driver-managed memory introduced >> in commit 75ac4c58bc0d ("mm/memory_hotplug: introduce >> add_memory_driver_managed()"). > > Is this commit id correct?
Good point, it's the one from next-20200605.
7b7b27214bba
Is the correct one.
[...]
> > Looks good to me. > Reviewed-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com> >
Thanks!
-- Thanks,
David / dhildenb
| |