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, 28 Jun 2023 02:15:56 -0700 [thread overview]
Message-ID: <ZJv6TL4yH4HbCe/h@gmail.com> (raw)
In-Reply-To: <20230627223040.bjacsmaotlderpdu@desk>
On Tue, Jun 27, 2023 at 03:30:40PM -0700, Pawan Gupta wrote:
> On Tue, Jun 27, 2023 at 10:36:10AM -0700, Breno Leitao wrote:
> > On Wed, Jun 21, 2023 at 12:41:01PM -0700, Pawan Gupta wrote:
> > > On Wed, Jun 21, 2023 at 11:36:53AM -0700, Breno Leitao wrote:
> > > > If I understand where you want to go, you think we should create a
> > > > single patchset that creates a CONFIG_<MITIGATION> for each mitigation,
> > > > and move get it under CONFIG_SPECULATION_MITIGATIONS.
> > >
> > > Yes, a single series (or a patch) that adds config for each mitigation
> > > would be good.
> >
> > I've been working on this request, and I may need your help to validate
> > the wordings and dependencies (as in architecture/vendors where the
> > problem needs to be mitigations) for each entry.
>
> Kconfig text looks fine to me. (Some comments on arch/vendor dependency
> are down below).
Neat, thanks for the clarifications. I will send v3 later today.
prev parent reply other threads:[~2023-06-28 9:27 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
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 [this message]
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=ZJv6TL4yH4HbCe/h@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.