mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Borislav Petkov <bp@alien8.de>
Cc: jpoimboe@kernel.org, mingo@redhat.com, x86@kernel.org,
	tglx@linutronix.de, linux-kernel@vger.kernel.org,
	pawan.kumar.gupta@linux.intel.com
Subject: Re: [PATCH v3 00/10] x86/bugs: Separate config for mitigations
Date: Mon, 29 Jul 2024 09:27:10 -0700	[thread overview]
Message-ID: <ZqfC3me0aC3N1iUQ@gmail.com> (raw)
In-Reply-To: <20240729092102.GAZqde_tdP_Ca-chhl@fat_crate.local>

Hello Borislav,

On Mon, Jul 29, 2024 at 11:21:02AM +0200, Borislav Petkov wrote:
> On Mon, Apr 22, 2024 at 09:58:14AM -0700, Breno Leitao wrote:
> > Breno Leitao (10):
> >   x86/bugs: Add a separate config for GDS
> >   x86/bugs: Add a separate config for MDS
> >   x86/bugs: Add a separate config for TAA
> >   x86/bugs: Add a separate config for MMIO Stable Data
> >   x86/bugs: Add a separate config for L1TF
> >   x86/bugs: Add a separate config for RETBLEED
> >   x86/bugs: Add a separate config for Spectre v1
> >   x86/bugs: Add a separate config for SRBDS
> >   x86/bugs: Add a separate config for Spectre V2
> >   x86/bugs: Add a separate config for SSB
> > 
> >  arch/x86/Kconfig           | 117 +++++++++++++++++++++++++++++++++++--
> >  arch/x86/kernel/cpu/bugs.c |  46 +++++++++------
> >  2 files changed, 140 insertions(+), 23 deletions(-)
> 
> Ok, rest looks ok. You can send a new version with all feedback addressed.

Thanks for reviewing it.

I will send a v4, where I will drop MITIGATION_GDS_FORCE, and keep only
MITIGATION_GDS Kconfig config entry.

Thanks,
--breno

      reply	other threads:[~2024-07-29 16:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 16:58 Breno Leitao
2024-04-22 16:58 ` [PATCH v3 01/10] x86/bugs: Add a separate config for GDS Breno Leitao
2024-07-12 17:21   ` Borislav Petkov
2024-07-15 12:14     ` Breno Leitao
2024-07-15 12:17       ` Borislav Petkov
2024-07-15 13:35         ` Breno Leitao
2024-07-15 13:43           ` Borislav Petkov
2024-07-15 14:20             ` Breno Leitao
2024-07-16 18:51         ` Daniel Sneddon
2024-07-16 19:10           ` Borislav Petkov
2024-04-22 16:58 ` [PATCH v3 02/10] x86/bugs: Add a separate config for MDS Breno Leitao
2024-04-22 16:58 ` [PATCH v3 03/10] x86/bugs: Add a separate config for TAA Breno Leitao
2024-04-22 16:58 ` [PATCH v3 04/10] x86/bugs: Add a separate config for MMIO Stable Data Breno Leitao
2024-04-22 16:58 ` [PATCH v3 05/10] x86/bugs: Add a separate config for L1TF Breno Leitao
2024-04-22 16:58 ` [PATCH v3 06/10] x86/bugs: Add a separate config for RETBLEED Breno Leitao
2024-04-22 16:58 ` [PATCH v3 07/10] x86/bugs: Add a separate config for Spectre v1 Breno Leitao
2024-04-22 16:58 ` [PATCH v3 08/10] x86/bugs: Add a separate config for SRBDS Breno Leitao
2024-04-22 16:58 ` [PATCH v3 09/10] x86/bugs: Add a separate config for Spectre V2 Breno Leitao
2024-04-22 16:58 ` [PATCH v3 10/10] x86/bugs: Add a separate config for SSB Breno Leitao
2024-07-29  9:21 ` [PATCH v3 00/10] x86/bugs: Separate config for mitigations Borislav Petkov
2024-07-29 16:27   ` 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=ZqfC3me0aC3N1iUQ@gmail.com \
    --to=leitao@debian.org \
    --cc=bp@alien8.de \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.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
all inboxes | Powered by JetHome®