From: Yan Zhao <yan.y.zhao@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: selftests: Use "gpa" and "gva" for local variable names in pre-fault test
Date: Tue, 14 Oct 2025 09:37:08 +0800 [thread overview]
Message-ID: <aO2pROT5K+4J7j9k@yzhao56-desk.sh.intel.com> (raw)
In-Reply-To: <20251007224515.374516-1-seanjc@google.com>
On Tue, Oct 07, 2025 at 03:45:15PM -0700, Sean Christopherson wrote:
> Rename guest_test_{phys,virt}_mem to g{p,v}a in the pre-fault memory test
> to shorten line lengths and to use standard terminology.
>
> No functional change intended.
>
> Cc: Yan Zhao <yan.y.zhao@intel.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> .../selftests/kvm/pre_fault_memory_test.c | 27 +++++++++----------
> 1 file changed, 12 insertions(+), 15 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/pre_fault_memory_test.c b/tools/testing/selftests/kvm/pre_fault_memory_test.c
> index f04768c1d2e4..6db75946a4f8 100644
> --- a/tools/testing/selftests/kvm/pre_fault_memory_test.c
> +++ b/tools/testing/selftests/kvm/pre_fault_memory_test.c
> @@ -161,6 +161,7 @@ static void pre_fault_memory(struct kvm_vcpu *vcpu, u64 base_gpa, u64 offset,
>
> static void __test_pre_fault_memory(unsigned long vm_type, bool private)
> {
> + uint64_t gpa, gva, alignment, guest_page_size;
> const struct vm_shape shape = {
> .mode = VM_MODE_DEFAULT,
> .type = vm_type,
> @@ -170,35 +171,31 @@ static void __test_pre_fault_memory(unsigned long vm_type, bool private)
> struct kvm_vm *vm;
> struct ucall uc;
>
> - uint64_t guest_test_phys_mem;
> - uint64_t guest_test_virt_mem;
> - uint64_t alignment, guest_page_size;
> -
> vm = vm_create_shape_with_one_vcpu(shape, &vcpu, guest_code);
>
> alignment = guest_page_size = vm_guest_mode_params[VM_MODE_DEFAULT].page_size;
> - guest_test_phys_mem = (vm->max_gfn - TEST_NPAGES) * guest_page_size;
> + gpa = (vm->max_gfn - TEST_NPAGES) * guest_page_size;
> #ifdef __s390x__
> alignment = max(0x100000UL, guest_page_size);
> #else
> alignment = SZ_2M;
> #endif
> - guest_test_phys_mem = align_down(guest_test_phys_mem, alignment);
> - guest_test_virt_mem = guest_test_phys_mem & ((1ULL << (vm->va_bits - 1)) - 1);
> + gpa = align_down(gpa, alignment);
> + gva = gpa & ((1ULL << (vm->va_bits - 1)) - 1);
>
> - vm_userspace_mem_region_add(vm, VM_MEM_SRC_ANONYMOUS,
> - guest_test_phys_mem, TEST_SLOT, TEST_NPAGES,
> + vm_userspace_mem_region_add(vm, VM_MEM_SRC_ANONYMOUS, gpa,
Wrap at 80 characters?
> + TEST_SLOT, TEST_NPAGES,
> private ? KVM_MEM_GUEST_MEMFD : 0);
> - virt_map(vm, guest_test_virt_mem, guest_test_phys_mem, TEST_NPAGES);
> + virt_map(vm, gva, gpa, TEST_NPAGES);
>
> if (private)
> - vm_mem_set_private(vm, guest_test_phys_mem, TEST_SIZE);
> + vm_mem_set_private(vm, gpa, TEST_SIZE);
>
> - pre_fault_memory(vcpu, guest_test_phys_mem, 0, SZ_2M, 0, private);
> - pre_fault_memory(vcpu, guest_test_phys_mem, SZ_2M, PAGE_SIZE * 2, PAGE_SIZE, private);
> - pre_fault_memory(vcpu, guest_test_phys_mem, TEST_SIZE, PAGE_SIZE, PAGE_SIZE, private);
> + pre_fault_memory(vcpu, gpa, 0, SZ_2M, 0, private);
> + pre_fault_memory(vcpu, gpa, SZ_2M, PAGE_SIZE * 2, PAGE_SIZE, private);
> + pre_fault_memory(vcpu, gpa, TEST_SIZE, PAGE_SIZE, PAGE_SIZE, private);
>
> - vcpu_args_set(vcpu, 1, guest_test_virt_mem);
> + vcpu_args_set(vcpu, 1, gva);
Should we cleanup guest_code() as below?
-static void guest_code(uint64_t base_gpa)
+static void guest_code(uint64_t base_gva)
{
volatile uint64_t val __used;
int i;
for (i = 0; i < TEST_NPAGES; i++) {
- uint64_t *src = (uint64_t *)(base_gpa + i * PAGE_SIZE);
+ uint64_t *src = (uint64_t *)(base_gva + i * PAGE_SIZE);
val = *src;
}
> vcpu_run(vcpu);
>
> run = vcpu->run;
>
> base-commit: efcebc8f7aeeba15feb1a5bde70af74d96bf1a76
> --
> 2.51.0.710.ga91ca5db03-goog
>
>
next prev parent reply other threads:[~2025-10-14 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 22:45 [PATCH] KVM: selftests: Use "gpa" and "gva" for local variable names in pre-fault test Sean Christopherson
2025-10-14 1:37 ` Yan Zhao [this message]
2025-10-17 22:17 ` Sean Christopherson
2025-11-04 17:45 ` Sean Christopherson
2025-11-05 2:02 ` Yan Zhao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aO2pROT5K+4J7j9k@yzhao56-desk.sh.intel.com \
--to=yan.y.zhao@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.