From: Sean Christopherson <seanjc@google.com>
To: Hisam Mehboob <hisamshar@gmail.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] KVM: selftests: Replace ulong with unsigned long
Date: Tue, 18 Aug 2026 09:27:50 -0700 [thread overview]
Message-ID: <aoSIBnFfy4osa6wt@google.com> (raw)
In-Reply-To: <8d069fe1-a5b6-4a86-9604-26aebe2dc243@gmail.com>
On Tue, Aug 18, 2026, Hisam Mehboob wrote:
> On 8/18/26 03:24, Sean Christopherson wrote:
> > On Tue, Aug 18, 2026, Hisam Mehboob wrote:
> > > Gentle ping on this patch; it has been on the list since Aug 3 without
> > > any comments.
> >
> > Patience, please. This is on my list of things to grab for 7.4. You posted right
> > at the end of a cycle, shortly before the merge window, and the code in question
> > has existed for years, i.e. it didn't seem urgent enough to squeeze into 7.3.
> >
> > If this is the very last thing needed to unblock musl builds of KVM selftests,
> > than that changes things, but IIRC there are other "fix selftests builds with musl"
> > patches floating around.
>
> No, this isn't the last blocker. I verified with musl-gcc on x86_64:
> with only this patch applied, the build still fails in steal_time.c on
> pthread_attr_setaffinity_np() -- it also needs your task-pinning fix
> ("KVM: selftests: Use KVM's task pinning APIs in steal_time", which I
> resent). With both applied, the musl build passes.
Oh, so on top of "https://github.com/kvm-x86/linux.git next", this *is* the last
blocker? If so, then I'll grab this for 7.3.
next prev parent reply other threads:[~2026-08-18 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 17:08 [PATCH v2] KVM: selftests: Replace ulong with unsigned long Hisam Mehboob
2026-08-17 22:04 ` Hisam Mehboob
2026-08-17 22:24 ` Sean Christopherson
2026-08-17 22:42 ` Hisam Mehboob
2026-08-18 16:27 ` Sean Christopherson [this message]
2026-08-18 18:19 ` Hisam Mehboob
2026-08-18 19:28 ` Sean Christopherson
2026-08-18 21:03 ` Hisam Mehboob
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=aoSIBnFfy4osa6wt@google.com \
--to=seanjc@google.com \
--cc=hisamshar@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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