[lkml]   [2020]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v3 2/3] mm: don't rely on system state to detect hot-plug operations
On Tue, Sep 15, 2020 at 11:41:42AM +0200, Laurent Dufour wrote:
> [1] According to Oscar Salvador, using this qemu command line, ACPI memory
> hotplug operations are raised at SYSTEM_SCHEDULING state:

I would like to stress that this is not the only way we can end up
hotplugging memor while state = SYSTEM_SCHEDULING.
According to David, we can end up doing this if we reboot a VM
with hotplugged memory.
(And I have seen other virtualization technologies do the same)

> Fixes: 4fbce633910e ("mm/memory_hotplug.c: make register_mem_sect_under_node() a callback of walk_memory_range()")
> Signed-off-by: Laurent Dufour <>
> Reviewed-by: David Hildenbrand <>
> Cc:
> Cc: Greg Kroah-Hartman <>
> Cc: "Rafael J. Wysocki" <>
> Cc: Andrew Morton <>
> Cc: Michal Hocko <>
> Cc: Oscar Salvador <>

Reviewed-by: Oscar Salvador <>

Oscar Salvador

 \ /
  Last update: 2020-09-15 12:32    [W:0.111 / U:1.980 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site