From: Breno Leitao <leitao@debian.org>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
leit@fb.com,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86/bugs: Break down mitigations configurations
Date: Wed, 21 Jun 2023 08:54:17 -0700 [thread overview]
Message-ID: <ZJMdKUr98H8zPSAl@gmail.com> (raw)
In-Reply-To: <20230621001327.qdyebewnx7r5aiy3@desk>
On Tue, Jun 20, 2023 at 05:13:27PM -0700, Pawan Gupta wrote:
> On Fri, Jun 16, 2023 at 09:48:50AM -0700, Breno Leitao wrote:
> > There is no way to disable MDS, TAA, MMIO Stale data mitigation today at
> > compilation time. These mitigations are enabled even if
> > CONFIG_SPECULATION_MITIGATIONS is unset.
> >
> > Create a new KCONFIG option for each mitigation under
> > CONFIG_SPECULATION_MITIGATIONS that allows these
> > mitigations to be disabled by default at compilation time.
>
> I don't think all mitigations are still controllable at build-time e.g.
> spectre_v2 eIBRS mitigation will still be deployed irrespective of the
> config.
Right. This patchset only cares about MDS, TAA and MMIO. I am more than
happy to send a new patch to also disable spectre_v2 eIBRS.
next prev parent reply other threads:[~2023-06-21 15:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 16:48 [PATCH v2] x86/bugs: Break down mitigations configurations Breno Leitao
2023-06-21 0:13 ` Pawan Gupta
2023-06-21 15:54 ` Breno Leitao [this message]
2023-06-21 17:31 ` Pawan Gupta
2023-06-21 18:36 ` Breno Leitao
2023-06-21 19:41 ` Pawan Gupta
2023-06-21 22:35 ` Dave Hansen
2023-06-21 22:52 ` Breno Leitao
2023-06-21 22:58 ` Dave Hansen
2023-06-22 12:42 ` Borislav Petkov
2023-06-22 13:42 ` Dave Hansen
2023-06-27 17:36 ` Breno Leitao
2023-06-27 22:30 ` Pawan Gupta
2023-06-28 9:15 ` Breno Leitao
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=ZJMdKUr98H8zPSAl@gmail.com \
--to=leitao@debian.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=leit@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.