[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220315181509.351704-1-tony.luck@intel.com>
Date: Tue, 15 Mar 2022 11:15:07 -0700
From: Tony Luck <tony.luck@...el.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Smita Koralahalli <Smita.KoralahalliChannabasappa@....com>,
hpa@...or.com, Dave Hansen <dave.hansen@...ux.intel.com>,
Yazen Ghannam <yazen.ghannam@....com>,
linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev, Tony Luck <tony.luck@...el.com>
Subject: [PATCH v2 0/2] New CMCI storm mitigation for Intel CPUs
Two-part motivation:
1) Disabling CMCI globally is an overly big hammer
2) Intel signals some UNCORRECTED errors using CMCI (yes, turns
out that was a poorly chosen name given the later evolution of
the architecture). Since we don't want to miss those, the proposed
storm code just bumps the threshold to (almost) maximum to mitigate,
but not eliminate the storm. Note that the threshold only applies
to corrected errors.
Patch 1 deletes the parts of the old storm code that are no
longer needed.
Patch 2 adds the new per-bank mitigation.
Smita: Unless Boris finds a some more stuff for me to fix, this
version will be a better starting point to merge with your changes.
Changes since v1 (based on feedback from Boris)
- Spelling fixes in commit message
- Many more comments explaining what is going on
- Change name of function that does tracking
- Change names for #defines for storm BEGIN/END
- #define for high threshold in decimal, not hex
Tony Luck (2):
x86/mce: Remove old CMCI storm mitigation code
x86/mce: Add per-bank CMCI storm mitigation
arch/x86/kernel/cpu/mce/core.c | 46 +++---
arch/x86/kernel/cpu/mce/intel.c | 241 ++++++++++++++---------------
arch/x86/kernel/cpu/mce/internal.h | 10 +-
3 files changed, 141 insertions(+), 156 deletions(-)
base-commit: ffb217a13a2eaf6d5bd974fc83036a53ca69f1e2
--
2.35.1
Powered by blists - more mailing lists