From: Sean Christopherson <seanjc@google.com>
To: kvm@vger.kernel.org, Maxim Levitsky <mlevitsk@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: selftests: memslot_perf_test: increase guest sync timeout
Date: Mon, 4 Nov 2024 21:55:28 -0800 [thread overview]
Message-ID: <ZymzUI3HnkYMxyjk@google.com> (raw)
In-Reply-To: <172848588854.1055233.16718265016131437325.b4-ty@google.com>
On Wed, Oct 09, 2024, Sean Christopherson wrote:
> On Fri, 04 Oct 2024 18:01:53 -0400, Maxim Levitsky wrote:
> > When memslot_perf_test is run nested, first iteration of test_memslot_rw_loop
> > testcase, sometimes takes more than 2 seconds due to build of shadow page tables.
> >
> > Following iterations are fast.
> >
> > To be on the safe side, bump the timeout to 10 seconds.
> >
> > [...]
>
> Nice timing (lol), the alarm can also fire spuriously when running selftests
> on a loaded arm64 host.
>
> Applied to kvm-x86 fixes, thanks!
>
> [1/1] KVM: selftests: memslot_perf_test: increase guest sync timeout
> https://github.com/kvm-x86/linux/commit/7d4e28327d7e
FYI, I rebased "fixes" onto 6.12-rc5 to avoid conflicts in other patches, new hash:
[1/1] KVM: selftests: memslot_perf_test: increase guest sync timeout
https://github.com/kvm-x86/linux/commit/2d0f2a648147
FWIW, I am planning on getting this to Paolo in time for -rc7.
prev parent reply other threads:[~2024-11-05 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 22:01 [PATCH] KVM: selftests: memslot_perf_test: increase guest sync timeout Maxim Levitsky
2024-10-07 14:02 ` Liam Merwick
2024-10-09 14:58 ` Sean Christopherson
2024-11-05 5:55 ` Sean Christopherson [this message]
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=ZymzUI3HnkYMxyjk@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.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