On 10.04.20 21:10, Andrew Morton wrote: > It's unclear (to me) what is the status of this patchset. But it does appear that > an new version can be expected? > I'd suggest to unqueue the patches until we have a consensus. While there are a couple of ideas floating around here, my current suggestion would be either 1. Indicate all hotplugged memory as "System RAM (hotplugged)" in /proc/iomem and the firmware memmap (on all architectures). This will require kexec changes, but I would have assume that kexec has to be updated in lock-step with the kernel just like e.g., makedumpfile. Modify kexec() to not place the kexec kernel on these areas (easy) but still consider them as crash regions to dump. When loading a kexec kernel, validate in the kernel that the memory is appropriate. 2. Make kexec() reload the the kernel whenever we e.g., get a udev event for removal of memory in /sys/devices/system/memory/. On every remove_memory(), invalidate the loaded kernel in the kernel. As I mentioned somewhere, 1. will be interesting for virtio-mem, where we don't want any kexec kernel to be placed on virtio-mem-added memory. -- Thanks, David / dhildenb _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
