On Tue, Jan 12, 2021, Ben Gardon wrote: > Add a memslot modification stress test in which a memslot is repeatedly > created and removed while vCPUs access memory in another memslot. Most > userspaces do not create or remove memslots on running VMs which makes > it hard to test races in adding and removing memslots without a > dedicated test. Adding and removing a memslot also has the effect of > tearing down the entire paging structure, which leads to more page > faults and pressure on the page fault handling path than a one-and-done > memory population test.
Would it make sense to integrate this with set_memory_region_test? At a high level, they are doing very similar things. Not sure how much code can be shared, but I assume there's some amount of overlap.
