From: Maxim Levitsky <mlevitsk@redhat.com>
To: kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] KVM: selftests: fix max_guest_memory_test with more that 256 vCPUs
Date: Tue, 02 Apr 2024 10:05:24 -0400 [thread overview]
Message-ID: <207d6598c8b74161efc38bd18b476ca8626786b1.camel@redhat.com> (raw)
In-Reply-To: <20240315143507.102629-1-mlevitsk@redhat.com>
On Fri, 2024-03-15 at 10:35 -0400, Maxim Levitsky wrote:
> max_guest_memory_test uses ucalls to sync with the host, but
> it also resets the guest RIP back to its initial value in between
> tests stages.
>
> This makes the guest never reach the code which frees the ucall struct
> and since a fixed pool of 512 ucall structs is used, the test starts
> to fail when more that 256 vCPUs are used.
>
> Fix that by replacing the manual register reset with a loop in
> the guest code.
>
> Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> ---
> .../testing/selftests/kvm/max_guest_memory_test.c | 15 ++++++---------
> 1 file changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/max_guest_memory_test.c b/tools/testing/selftests/kvm/max_guest_memory_test.c
> index 6628dc4dda89f3c..1a6da7389bf1f5b 100644
> --- a/tools/testing/selftests/kvm/max_guest_memory_test.c
> +++ b/tools/testing/selftests/kvm/max_guest_memory_test.c
> @@ -22,10 +22,11 @@ static void guest_code(uint64_t start_gpa, uint64_t end_gpa, uint64_t stride)
> {
> uint64_t gpa;
>
> - for (gpa = start_gpa; gpa < end_gpa; gpa += stride)
> - *((volatile uint64_t *)gpa) = gpa;
> -
> - GUEST_DONE();
> + for (;;) {
> + for (gpa = start_gpa; gpa < end_gpa; gpa += stride)
> + *((volatile uint64_t *)gpa) = gpa;
> + GUEST_SYNC(0);
> + }
> }
>
> struct vcpu_info {
> @@ -55,7 +56,7 @@ static void rendezvous_with_boss(void)
> static void run_vcpu(struct kvm_vcpu *vcpu)
> {
> vcpu_run(vcpu);
> - TEST_ASSERT_EQ(get_ucall(vcpu, NULL), UCALL_DONE);
> + TEST_ASSERT_EQ(get_ucall(vcpu, NULL), UCALL_SYNC);
> }
>
> static void *vcpu_worker(void *data)
> @@ -64,17 +65,13 @@ static void *vcpu_worker(void *data)
> struct kvm_vcpu *vcpu = info->vcpu;
> struct kvm_vm *vm = vcpu->vm;
> struct kvm_sregs sregs;
> - struct kvm_regs regs;
>
> vcpu_args_set(vcpu, 3, info->start_gpa, info->end_gpa, vm->page_size);
>
> - /* Snapshot regs before the first run. */
> - vcpu_regs_get(vcpu, ®s);
> rendezvous_with_boss();
>
> run_vcpu(vcpu);
> rendezvous_with_boss();
> - vcpu_regs_set(vcpu, ®s);
> vcpu_sregs_get(vcpu, &sregs);
> #ifdef __x86_64__
> /* Toggle CR0.WP to trigger a MMU context reset. */
Kind ping on this patch.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2024-04-02 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 14:35 [PATCH] KVM: selftests: fix max_guest_memory_test with more that 256 vCPUs Maxim Levitsky
2024-04-02 14:05 ` Maxim Levitsky [this message]
2024-04-02 23:06 ` Sean Christopherson
2024-04-09 2:01 ` Sean Christopherson
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=207d6598c8b74161efc38bd18b476ca8626786b1.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox