mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Chang S. Bae" <chang.seok.bae@intel.com>,
	<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
	<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
	<dave.hansen@linux.intel.com>, <tony.luck@intel.com>,
	Yan Hua Wu <yanhua1.wu@intel.com>,
	William Xie <william.xie@intel.com>,
	Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH 1/1] arch/x86/microcode/intel: Remove unnecessary cache writeback and invalidation
Date: Wed, 3 Jul 2024 13:50:37 -0700	[thread overview]
Message-ID: <ZoWZG75hFpfK6kkv@a4bf019067fa.jf.intel.com> (raw)
In-Reply-To: <0aa05063-c9ed-465d-a7d2-e5fa0bc6379a@intel.com>

On Mon, Jul 01, 2024 at 03:56:20PM -0700, Dave Hansen wrote:
> On 7/1/24 14:20, Chang S. Bae wrote:
> ...> Remove native_wbinvd() and update the erratum name to align with the
> > latest errata documentation.
> 
> I'm all for simplifying this code and also for removing any WBINVDs that
> we possibly can.  But it also makes me a wee bit nervous that this could
> have been hiding any _new_ issues (like the Broadwell one) had they
> crept in.
> 
> I'm tentatively in favor of this, but it's definitely the kind of thing
> we want to apply early and get maximum testing on.
> 
> I'd also appreciate an ack from Ashok on this one.

Thanks Dave. At the time when wbinvd() was added, there was no
confirmation that we didn't have any other products that slipped. This was
also during the meltdown timeframe, so big hammer was choosen for safety.

We attempted to remove them during the minrev rework.

https://lore.kernel.org/lkml/20230130213955.6046-9-ashok.raj@intel.com/

Agree that we must get wider testing. Only caveat is that you should find a
newer microcode to apply, which might be difficult for all products. Unless
there is a debug option to reload force the same rev in case you don't have
a newer ucode to test. Its good to get this in to reduce the big hammer
effect.

Acked by: Ashok Raj <ashok.raj@intel.com>

-- 
Cheers,
Ashok

  reply	other threads:[~2024-07-03 20:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 21:20 [PATCH 0/1] x86/microcode: Revert cache flush on Intel microcode loading Chang S. Bae
2024-07-01 21:20 ` [PATCH 1/1] arch/x86/microcode/intel: Remove unnecessary cache writeback and invalidation Chang S. Bae
2024-07-01 22:56   ` Dave Hansen
2024-07-03 20:50     ` Ashok Raj [this message]
2024-07-03 20:55       ` Dave Hansen
2024-07-03 21:03         ` Ashok Raj
2024-07-03 21:11           ` Dave Hansen
2024-07-03 21:33             ` Ashok Raj
2024-07-04  0:05               ` Chang S. Bae
2024-07-02 23:24   ` Chang S. Bae
2024-09-10 18:35   ` Chang S. Bae

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=ZoWZG75hFpfK6kkv@a4bf019067fa.jf.intel.com \
    --to=ashok.raj@intel.com \
    --cc=bp@alien8.de \
    --cc=chang.seok.bae@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=william.xie@intel.com \
    --cc=x86@kernel.org \
    --cc=yanhua1.wu@intel.com \
    /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

Powered by JetHome