linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Breno Leitao <leitao@debian.org>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	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: Thu, 22 Jun 2023 14:42:38 +0200	[thread overview]
Message-ID: <20230622124238.GAZJRBvrJdWloWzy0D@fat_crate.local> (raw)
In-Reply-To: <0c908258-2b03-ebb3-bc7d-af5ea66479d4@intel.com>

On Wed, Jun 21, 2023 at 03:58:10PM -0700, Dave Hansen wrote:
> Do you like the direction this is going?  Maybe I'm missing something.

Yeah, see

f43b9876e857 ("x86/retbleed: Add fine grained Kconfig knobs")

AFAIR, Linus wanted those this way so the only logical next step is to
add the Kconfig knobs for the missing ones...

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2023-06-22 12:43 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 [this message]
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=20230622124238.GAZJRBvrJdWloWzy0D@fat_crate.local \
    --to=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=leit@fb.com \
    --cc=leitao@debian.org \
    --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 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).