On Mon, May 27, 2019 at 01:11:51PM +0200, David Hildenbrand wrote: > We really don't want anything during memory hotunplug to fail. > We always pass a valid memory block device, that check can go. Avoid > allocating memory and eventually failing. As we are always called under > lock, we can use a static piece of memory. This avoids having to put > the structure onto the stack, having to guess about the stack size > of callers. > > Patch inspired by a patch from Oscar Salvador. > > In the future, there might be no need to iterate over nodes at all. > mem->nid should tell us exactly what to remove. Memory block devices > with mixed nodes (added during boot) should properly fenced off and never > removed. > > Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org> > Cc: "Rafael J. Wysocki" <raf...@kernel.org> > Cc: Alex Deucher <alexander.deuc...@amd.com> > Cc: "David S. Miller" <da...@davemloft.net> > Cc: Mark Brown <broo...@kernel.org> > Cc: Chris Wilson <ch...@chris-wilson.co.uk> > Cc: David Hildenbrand <da...@redhat.com> > Cc: Oscar Salvador <osalva...@suse.de> > Cc: Andrew Morton <a...@linux-foundation.org> > Cc: Jonathan Cameron <jonathan.came...@huawei.com> > Signed-off-by: David Hildenbrand <da...@redhat.com>
Reviewed-by: Oscar Salvador <osalva...@suse.de> -- Oscar Salvador SUSE L3
