From: Borislav Petkov <bp@alien8.de>
To: Reiji Watanabe <reijiw@google.com>
Cc: Ramakrishna Saripalli <rsaripal@amd.com>,
linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, Jonathan Corbet <corbet@lwn.net>,
bsd@redhat.com
Subject: Re: [PATCH v4 1/1] x86/cpufeatures: Implement Predictive Store Forwarding control.
Date: Fri, 30 Apr 2021 21:56:57 +0200 [thread overview]
Message-ID: <YIxhCSt6t5U/Eldb@zn.tnic> (raw)
In-Reply-To: <CAAeT=Fw-nt5h3DhRCQr8Ma71NiP7dHB+WD2hie_55SpCHR=mDQ@mail.gmail.com>
On Fri, Apr 30, 2021 at 12:42:46PM -0700, Reiji Watanabe wrote:
> Then, it would be a problem if its guests want to use PSFD looking at
> x86_virt_spec_ctrl().
Well, will they want to do that? If so, why? Use case?
We decided to do this lite version to give people the opportunity to
evaluate whether there's a need to make full-blown mitigation-like,
per-thread thing like the rest of the mitigations in bugs.c or leave it
to be a chicken-bit thing.
So do you have any particular use case in mind or are you simply poking
holes in this?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-04-30 19:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 13:17 [PATCH v4 0/1] Introduce support for PSF control Ramakrishna Saripalli
2021-04-30 13:17 ` [PATCH v4 1/1] x86/cpufeatures: Implement Predictive Store Forwarding control Ramakrishna Saripalli
2021-04-30 14:50 ` Tom Lendacky
2021-04-30 14:56 ` Saripalli, RK
2021-04-30 19:42 ` Reiji Watanabe
2021-04-30 19:52 ` Saripalli, RK
2021-05-01 1:50 ` Reiji Watanabe
2021-05-04 21:01 ` Saripalli, RK
2021-05-04 22:11 ` Reiji Watanabe
2021-05-05 1:13 ` Saripalli, RK
2021-04-30 19:56 ` Borislav Petkov [this message]
2021-04-30 21:03 ` Reiji Watanabe
2021-04-30 21:11 ` Borislav Petkov
2021-05-01 1:01 ` Reiji Watanabe
2021-05-05 0:11 ` Pawan Gupta
2021-05-05 1:11 ` Saripalli, RK
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=YIxhCSt6t5U/Eldb@zn.tnic \
--to=bp@alien8.de \
--cc=bsd@redhat.com \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reijiw@google.com \
--cc=rsaripal@amd.com \
--cc=tglx@linutronix.de \
--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).