[PATCH RFC] mm/memory_hotplug: Introduce memory block types
    Michal Suchánek 
    msuchanek at suse.de
       
    Fri Oct  5 03:50:10 AEST 2018
    
    
  
On Thu, 4 Oct 2018 17:45:13 +0200
David Hildenbrand <david at redhat.com> wrote:
> On 04/10/2018 17:28, Michal Suchánek wrote:
> > 
> > The state of the art is to determine what to do with hotplugged
> > memory in userspace based on platform and virtualization type.  
> 
> Exactly.
> 
> > 
> > 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
    
    
More information about the Linuxppc-dev
mailing list