From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Manali Shukla <manali.shukla@amd.com>,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
pbonzini@redhat.com, nikunj@amd.com, thomas.lendacky@amd.com
Subject: Re: [PATCH v4 2/5] x86/cpufeatures: Add CPUID feature bit for the Bus Lock Threshold
Date: Thu, 10 Apr 2025 16:25:48 -0700 [thread overview]
Message-ID: <Z_hTfFupiBFPHwVe@google.com> (raw)
In-Reply-To: <20250409092147.GAZ_Y8K52Opcw2X-tg@fat_crate.local>
On Wed, Apr 09, 2025, Borislav Petkov wrote:
> On Wed, Apr 09, 2025 at 11:30:56AM +0530, Manali Shukla wrote:
> > Do you have concern with the decision to expose the flag to /proc/cpuinfo?
> >
> > The decision to expose the flag to /proc/cpuinfo was already discussed in
> > [v1]. As suggested in the discussion [v1], I have added "buslock" to be
> > enumerated in /proc/cpuinfo.
>
> If you mean this:
>
> https://lore.kernel.org/kvm/20240709175145.9986-4-manali.shukla@amd.com/T/#m1dc7e08c54dd91d53a6bc5b1ed0a6721b356a756
>
> I don't see any conclusion there.
>
> I see Sean wanting to export information out of KVM to say what it supports
> without adding user ABI and I don't know how far that has come
Not very far :-(
> but what you're
> doing here ain't it.
>
> Just do:
>
> #define X86_FEATURE_BUS_LOCK_THRESHOLD (15*32+29) /* Bus lock threshold */
>
> and then later KVM can export this however it prefers.
+1
next prev parent reply other threads:[~2025-04-10 23:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 13:02 [PATCH v4 0/5] Add support for the Bus Lock Threshold Manali Shukla
2025-03-24 13:02 ` [PATCH v4 1/5] KVM: x86: Preparatory patch to move linear_rip out of kvm_pio_request Manali Shukla
2025-04-23 15:22 ` Sean Christopherson
2025-03-24 13:02 ` [PATCH v4 2/5] x86/cpufeatures: Add CPUID feature bit for the Bus Lock Threshold Manali Shukla
2025-03-24 21:56 ` Borislav Petkov
2025-04-09 6:00 ` Manali Shukla
2025-04-09 9:21 ` Borislav Petkov
2025-04-10 23:25 ` Sean Christopherson [this message]
2025-04-23 5:58 ` Manali Shukla
2025-03-24 13:02 ` [PATCH v4 3/5] KVM: SVM: Enable Bus lock threshold exit Manali Shukla
2025-04-16 6:00 ` Xiaoyao Li
2025-04-23 6:15 ` Manali Shukla
2025-04-23 15:29 ` Sean Christopherson
2025-04-30 11:15 ` Manali Shukla
2025-03-24 13:02 ` [PATCH v4 4/5] KVM: SVM: Add support for KVM_CAP_X86_BUS_LOCK_EXIT on SVM CPUs Manali Shukla
2025-04-16 6:14 ` Xiaoyao Li
2025-04-23 11:26 ` Manali Shukla
2025-04-23 15:30 ` Sean Christopherson
2025-04-30 11:18 ` Manali Shukla
2025-04-23 15:44 ` Sean Christopherson
2025-04-30 11:30 ` Manali Shukla
2025-03-24 13:02 ` [PATCH v4 5/5] KVM: selftests: Add bus lock exit test Manali Shukla
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=Z_hTfFupiBFPHwVe@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=manali.shukla@amd.com \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=thomas.lendacky@amd.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;
as well as URLs for NNTP newsgroup(s).