Thread (36 messages) 36 messages, 5 authors, 2018-11-27

Re: [PATCH RFC] mm/memory_hotplug: Introduce memory block types

From: Michal Suchánek <hidden>
Date: 2018-10-04 17:50:17
Also in: linux-acpi, linux-mm

On Thu, 4 Oct 2018 17:45:13 +0200
David Hildenbrand [off-list ref] wrote:
On 04/10/2018 17:28, Michal Suchánek wrote:
quoted
The state of the art is to determine what to do with hotplugged
memory in userspace based on platform and virtualization type.  
Exactly.
quoted
Changing the default to depend on the driver that added the memory
rather than platform type should solve the issue of VMs growing
different types of memory device emulation.  
Yes, my original proposal (this patch) was to handle it in the kernel
for known types. But as we learned, there might be some use cases that
might still require to make a decision in user space.

So providing the user space either with some type hint (auto-online
vs. standby) or the driver that added it (system vs. hyper-v ...)
would solve the issue.
Is that not available in the udev event?

Thanks

Michal
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help