From: Dave Hansen <dave.hansen@intel.com>
To: "Chang S. Bae" <chang.seok.bae@intel.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, tony.luck@intel.com,
ashok.raj@intel.com, Yan Hua Wu <yanhua1.wu@intel.com>,
William Xie <william.xie@intel.com>
Subject: Re: [PATCH 1/1] arch/x86/microcode/intel: Remove unnecessary cache writeback and invalidation
Date: Mon, 1 Jul 2024 15:56:20 -0700 [thread overview]
Message-ID: <0aa05063-c9ed-465d-a7d2-e5fa0bc6379a@intel.com> (raw)
In-Reply-To: <20240701212012.21499-2-chang.seok.bae@intel.com>
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.
next prev parent reply other threads:[~2024-07-01 22:56 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 [this message]
2024-07-03 20:50 ` Ashok Raj
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=0aa05063-c9ed-465d-a7d2-e5fa0bc6379a@intel.com \
--to=dave.hansen@intel.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@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