On Tue, May 07, 2019 at 10:36:55AM -0700, Matthew Wilcox wrote:
On Tue, May 07, 2019 at 07:32:24PM +0200, Michal Hocko wrote:
On Tue 07-05-19 13:18:06, Sasha Levin wrote:
> Michal, is there a testcase I can plug into kselftests to make sure we
> got this right (and don't regress)? We care a lot about memory hotplug
> working right.
As said in other email. The memory hotplug tends to work usually. It
takes unexpected memory layouts which trigger corner cases. This makes
testing really hard.
Can we do something with qemu? Is it flexible enough to hotplug memory
at the right boundaries?
That was my thinking too. qemu should be able to reproduce all these
"unexpected" memory layouts we've had issue with so far and at the very
least make sure we don't regress on those.
We're going to have (quite a) large amount of systems with "weird"
memory layouts that do memory hotplug quite frequently in production, so
this whole "tends to work usually" thing kinda scares me.
--
Thanks,
Sasha
