On Mon, Jan 29, 2024 at 09:32:15AM -0800, Sean Christopherson wrote:
> On Mon, Jan 29, 2024, Tao Su wrote:
> > On Fri, Jan 26, 2024 at 12:39:49PM -0800, Sean Christopherson wrote:
> > > +David
> > >
> >
> > [ ... ]
> >
> > > >
> > > > /*
> > > > @@ -192,7 +193,6 @@ static void run_test(enum vm_guest_mode mode, void *unused)
> > > > * memory again, the page counts should be the same as they were
> > > > * right after initial population of memory.
> > > > */
> > > > - TEST_ASSERT_EQ(stats_populated.pages_4k, stats_repopulated.pages_4k);
> > > > TEST_ASSERT_EQ(stats_populated.pages_2m, stats_repopulated.pages_2m);
> > > > TEST_ASSERT_EQ(stats_populated.pages_1g, stats_repopulated.pages_1g);
> > >
> > > Isn't it possible that something other than guest data could be mapped by THP
> > > hugepage, and that that hugepage could get shattered between the initial run and
> > > the re-population run?
> >
> > Good catch, I found that if the backing source is specified as THP, all hugepages
> > can also be migrated.
>
> The backing source for the test slots? Using THP is inherently fragile for this
> test, and IMO is firmly out of scope.
Yes, the user can optionally specify the backing source of test slots, e.g.,
./x86_64/dirty_log_page_splitting_test -s anonymous_thp
but we already have a hint: “This test will only work reliably with HugeTLB memory.
It can work with THP, but that is best effort.”
> I was talking about any memslots allocated by the core library, e.g. for the
> test's code and page tables. Those should be forced to be MADV_NOHUGEPAGE,
> though if the allocations are smaller than 2MiB (I forget how much we allocate),
> that would suffice for now.
The "other" memslot is more than 2MiB, and in this test, the memory that the guest
can touch in "other" memslot also exceeds 2MiB. It seems that the existing code has
forced the memory of VM_MEM_SRC_ANONYMOUS to MADV_NOHUGEPAGE, e.g.,
in vm_userspace_mem_region_add():
ret = madvise(region->host_mem, npages * vm->page_size,
src_type == VM_MEM_SRC_ANONYMOUS ? MADV_NOHUGEPAGE : MADV_HUGEPAGE);
>
> If we ensure the other memslots can only use 4KiB, then it's only the *.pages_4k
> checks that are problematic. Then the hugepage counts can be precise.
Yes, I see.
>
> Something like this is what I'm thinking (again, assuming the "other" memslot
> created by the library can't use THP).
The below code looks good to me and test PASS in our machine.
Thanks,
Tao
>
> ---
> .../x86_64/dirty_log_page_splitting_test.c | 21 +++++++++++--------
> 1 file changed, 12 insertions(+), 9 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/x86_64/dirty_log_page_splitting_test.c b/tools/testing/selftests/kvm/x86_64/dirty_log_page_splitting_test.c
> index 634c6bfcd572..4864cf3fae57 100644
> --- a/tools/testing/selftests/kvm/x86_64/dirty_log_page_splitting_test.c
> +++ b/tools/testing/selftests/kvm/x86_64/dirty_log_page_splitting_test.c
> @@ -92,7 +92,6 @@ static void run_test(enum vm_guest_mode mode, void *unused)
> uint64_t host_num_pages;
> uint64_t pages_per_slot;
> int i;
> - uint64_t total_4k_pages;
> struct kvm_page_stats stats_populated;
> struct kvm_page_stats stats_dirty_logging_enabled;
> struct kvm_page_stats stats_dirty_pass[ITERATIONS];
> @@ -107,6 +106,9 @@ static void run_test(enum vm_guest_mode mode, void *unused)
> guest_num_pages = vm_adjust_num_guest_pages(mode, guest_num_pages);
> host_num_pages = vm_num_host_pages(mode, guest_num_pages);
> pages_per_slot = host_num_pages / SLOTS;
> + TEST_ASSERT_EQ(host_num_pages, pages_per_slot * SLOTS);
> + TEST_ASSERT(!(host_num_pages % 512),
> + "Number of pages, '%lu' not a multiple of 2MiB", host_num_pages);
>
> bitmaps = memstress_alloc_bitmaps(SLOTS, pages_per_slot);
>
> @@ -165,10 +167,8 @@ static void run_test(enum vm_guest_mode mode, void *unused)
> memstress_free_bitmaps(bitmaps, SLOTS);
> memstress_destroy_vm(vm);
>
> - /* Make assertions about the page counts. */
> - total_4k_pages = stats_populated.pages_4k;
> - total_4k_pages += stats_populated.pages_2m * 512;
> - total_4k_pages += stats_populated.pages_1g * 512 * 512;
> + TEST_ASSERT_EQ((stats_populated.pages_2m * 512 +
> + stats_populated.pages_1g * 512 * 512), host_num_pages);
>
> /*
> * Check that all huge pages were split. Since large pages can only
> @@ -180,19 +180,22 @@ static void run_test(enum vm_guest_mode mode, void *unused)
> */
> if (dirty_log_manual_caps) {
> TEST_ASSERT_EQ(stats_clear_pass[0].hugepages, 0);
> - TEST_ASSERT_EQ(stats_clear_pass[0].pages_4k, total_4k_pages);
> + TEST_ASSERT(stats_clear_pass[0].pages_4k >= host_num_pages,
> + "Expected at least '%lu' 4KiB pages, found only '%lu'",
> + host_num_pages, stats_clear_pass[0].pages_4k);
> TEST_ASSERT_EQ(stats_dirty_logging_enabled.hugepages, stats_populated.hugepages);
> } else {
> TEST_ASSERT_EQ(stats_dirty_logging_enabled.hugepages, 0);
> - TEST_ASSERT_EQ(stats_dirty_logging_enabled.pages_4k, total_4k_pages);
> + TEST_ASSERT(stats_dirty_logging_enabled.pages_4k >= host_num_pages,
> + "Expected at least '%lu' 4KiB pages, found only '%lu'",
> + host_num_pages, stats_clear_pass[0].pages_4k);
> }
>
> /*
> * Once dirty logging is disabled and the vCPUs have touched all their
> - * memory again, the page counts should be the same as they were
> + * memory again, the hugepage counts should be the same as they were
> * right after initial population of memory.
> */
> - TEST_ASSERT_EQ(stats_populated.pages_4k, stats_repopulated.pages_4k);
> TEST_ASSERT_EQ(stats_populated.pages_2m, stats_repopulated.pages_2m);
> TEST_ASSERT_EQ(stats_populated.pages_1g, stats_repopulated.pages_1g);
> }
>
> base-commit: 0762cdfe8ee16e4035b0ad27418686ef0452932f
> --
>
