Re: [PATCH v4 1/9] KVM: selftest: Create KVM selftest runner
Ackerley Tng <[email protected]>
| Newsgroups | org.infradead.lists.kvm-riscv,dev.linux.lists.kvmarm,org.kernel.vger.kvm |
|---|---|
| Message-ID | <CAEvNRgE-qt8DAjOeE5ANpXzrgEKs+2_wh4YSmY=pe6krngBXqQ@mail.gmail.com> |
Sean Christopherson <[email protected]> writes: > On Wed, Jun 10, 2026, Ackerley Tng wrote: >> Vipin Sharma <[email protected]> writes: >> My (future) use case is that with hugepages, I want to run something >> like >> >> ./guest_memfd_test --order=0 >> ./guest_memfd_test --order=9 >> ./guest_memfd_test --order=18 >> >> And 0, 9 and 18 are the supported HugeTLB orders on the machine being >> tested. I'd like to iterate over supported HugeTLB orders at runner >> runtime instead of at build time. > > No. The right way to handle this is to define testcases for the "interesting" > sizes, and then rely on the test itself to SKIP if the size is unsupported. This > is no different than a test that requires EPT, or nested VMX, or nested SVM, etc. That should work too. So at build time I'd make it define all the possible HugeTLB sizes on every arch, and then skip as necessary. Why though, why not find the supported sizes at runtime? -- kvm-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kvm-riscv