From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Hisam Mehboob <hisamshar@gmail.com>,
Aqib Faruqui <aqibaf@amazon.com>,
Sean Christopherson <seanjc@google.com>
Subject: [PATCH v2 0/2] KVM: selftest: Fix steal time w/ non-glibc builds
Date: Tue, 7 Jul 2026 08:07:04 -0700 [thread overview]
Message-ID: <20260707150706.1198541-1-seanjc@google.com> (raw)
Remove unnecessary usage of pthread_attr_setaffinity_np() in the steal time
test so that it can build against non-glibc libraries, and opportunistically
expand the test coverage by pinning the test threads to a random pCPU instead
of hardcoding the pin to pCPU0.
v2:
- Rely on CPU affinity inheritance. [Sashiko]
- Add a patch to in to a random CPU instead of CPU0.
v1: https://lore.kernel.org/all/20260706163649.155548-1-hisamshar@gmail.com
Sean Christopherson (2):
KVM: selftests: Drop superfluous use of pthread_attr_setaffinity_np()
KVM: selftests: Randomize pCPU in steal time test
tools/testing/selftests/kvm/steal_time.c | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
base-commit: a204badd8432f93b7e862e7dac6db0fe3d65f370
--
2.55.0.rc2.803.g1fd1e6609c-goog
next reply other threads:[~2026-07-07 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 15:07 Sean Christopherson [this message]
2026-07-07 15:07 ` [PATCH v2 1/2] KVM: selftests: Drop superfluous use of pthread_attr_setaffinity_np() Sean Christopherson
2026-07-07 15:21 ` sashiko-bot
2026-07-07 16:03 ` Sean Christopherson
2026-07-07 15:07 ` [PATCH v2 2/2] KVM: selftests: Randomize pCPU in steal time test Sean Christopherson
2026-07-07 15:29 ` sashiko-bot
2026-07-07 16:15 ` 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=20260707150706.1198541-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=aqibaf@amazon.com \
--cc=hisamshar@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox