linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Sneddon <daniel.sneddon@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, hpa@zytor.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, pawan.kumar.gupta@linux.intel.com
Subject: Re: [PATCH 1/2] x86/bugs: Check VERW mitigations for consistency
Date: Tue, 29 Oct 2024 07:35:41 -0700	[thread overview]
Message-ID: <9ef41b96-8b96-441e-b053-4d7c7d9aa74a@linux.intel.com> (raw)
In-Reply-To: <20241029113911.GVZyDJX3rg8kh_4kYb@fat_crate.local>

On 10/29/24 04:39, Borislav Petkov wrote:
> On Mon, Oct 28, 2024 at 04:50:34PM -0700, Daniel Sneddon wrote:
>> There are currently 4 mitigations that use VERW: MDS, TAA,
>> MMIO Stale Data, and Register File Data Sampling. Because
>> all 4 use the same mitigation path, if any one of them is
>> enabled, they're all enabled. Normally, this is what is
>> wanted. However, if a user wants to disable the mitigation,
>> this can cause problems. If the user misses disabling even
>> one of these mitigations, then none of them will be
>> disabled. This can cause confusion as the user expects to
>> regain the performance lost to the mitigation but isn't
>> seeing any improvement. Since there are already 4 knobs for
>> controlling it, adding a 5th knob that controls all 4
>> mitigations together would just overcomplicate things.
>> Instead, let the user know their mitigations are out of sync
>> when at least one of these mitigations is disabled but not
>> all 4.
> 
> Please split this commit message into smaller chunks for better readability.
> For example:
> 
>     There are currently 4 mitigations that use VERW: MDS, TAA, MMIO Stale Data,
>     and Register File Data Sampling. Because all 4 use the same mitigation path,
>     if any one of them is enabled, they're all enabled.
>     
>     Normally, this is what is wanted. However, if a user wants to disable the
>     mitigation, this can cause problems. If the user misses disabling even one of
>     these mitigations, then none of them will be disabled.
>     
>     This can cause confusion as the user expects to regain the performance lost to
>     the mitigation but isn't seeing any improvement. Since there are already
>     4 knobs for controlling it, adding a 5th knob that controls all 4 mitigations
>     together would just overcomplicate things.
>     
>     Instead, let the user know their mitigations are out of sync when at least one
>     of these mitigations is disabled but not all 4.
> 
> Thx.
> 

Will do.

  reply	other threads:[~2024-10-29 14:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 23:50 [PATCH 0/2] VERW based clean-up Daniel Sneddon
2024-10-28 23:50 ` [PATCH 1/2] x86/bugs: Check VERW mitigations for consistency Daniel Sneddon
2024-10-29 11:39   ` Borislav Petkov
2024-10-29 14:35     ` Daniel Sneddon [this message]
2024-10-29 16:32   ` Nikolay Borisov
2024-10-29 16:34     ` Daniel Sneddon
2024-10-28 23:50 ` [PATCH 2/2] x86/bugs: Clean-up verw mitigations Daniel Sneddon
2024-10-29 11:37   ` Borislav Petkov
2024-10-29 14:40     ` Daniel Sneddon
2024-10-29 15:00       ` Borislav Petkov
2024-10-29 15:33         ` Daniel Sneddon
2024-10-29 16:37           ` Borislav Petkov
2024-10-29 16:39             ` Daniel Sneddon
2024-10-28 23:53 ` [PATCH 0/2] VERW based clean-up Daniel Sneddon

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=9ef41b96-8b96-441e-b053-4d7c7d9aa74a@linux.intel.com \
    --to=daniel.sneddon@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-doc@vger.kernel.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).