From: Paolo Bonzini <pbonzini@redhat.com>
To: Jim Mattson <jmattson@google.com>, Babu Moger <babu.moger@amd.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, hpa@zytor.com, seanjc@google.com,
vkuznets@redhat.com, wanpengli@tencent.com, joro@8bytes.org,
tony.luck@intel.com, peterz@infradead.org,
kyung.min.park@intel.com, wei.huang2@amd.com, jgross@suse.com,
andrew.cooper3@citrix.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Expose Predictive Store Forwarding Disable
Date: Wed, 24 Aug 2022 19:13:50 +0200 [thread overview]
Message-ID: <e3718025-682d-469c-eac9-b4995e91dc11@redhat.com> (raw)
In-Reply-To: <CALMp9eSKcwChbc=cgYpdrTCtt49S1uuRdYoe83yph3tXGN6a2Q@mail.gmail.com>
On 8/23/22 23:26, Jim Mattson wrote:
> For consistency, should this feature be renamed AMD_PSFD, now that
> Intel is enumerating PSFD with CPUID.(EAX=7,ECX=2):EDX.PSFD[bit 0]?
> Seehttps://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/technical-documentation/cpuid-enumeration-and-architectural-msrs.html.
>
> And, Paolo, why are we carrying X86_FEATURE_PSFD as a private #define
> in KVM rather than putting it where it belongs in cpufeatures.h?
>
Borislav asked to not show psfd in /proc/cpuinfo, because Linux had
decided not to control PSF separately; instead it just piggybacked
on SSBD which should disable PSF as well. Honestly I disagree but
it's not my area of maintenance.
Paolo
next prev parent reply other threads:[~2022-08-24 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <163244601049.30292.5855870305350227855.stgit@bmoger-ubuntu>
2021-09-27 10:59 ` [PATCH] KVM: x86: Expose Predictive Store Forwarding Disable Borislav Petkov
2021-09-27 11:13 ` Paolo Bonzini
2021-09-27 12:06 ` Borislav Petkov
2021-09-27 12:14 ` Paolo Bonzini
2021-09-27 12:28 ` Borislav Petkov
2021-09-27 12:54 ` Paolo Bonzini
2021-09-27 13:38 ` Borislav Petkov
2021-09-27 15:47 ` Babu Moger
2021-09-27 15:48 ` Borislav Petkov
2021-09-28 16:04 ` Paolo Bonzini
2021-09-29 20:27 ` Babu Moger
2021-09-30 13:41 ` Paolo Bonzini
2021-09-30 14:12 ` Babu Moger
2022-08-23 21:26 ` Jim Mattson
2022-08-24 17:13 ` Paolo Bonzini [this message]
2022-08-24 17:16 ` Jim Mattson
2022-08-26 10:10 ` Paolo Bonzini
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=e3718025-682d-469c-eac9-b4995e91dc11@redhat.com \
--to=pbonzini@redhat.com \
--cc=andrew.cooper3@citrix.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=kyung.min.park@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=wei.huang2@amd.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).