From: Tony Luck <tony.luck@intel.com>
To: linux-edac@vger.kernel.org
Cc: Tony Luck <tony.luck@intel.com>,
Aristeu Rozanski <aris@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Youquan Song <youquan.song@intel.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: [PATCH 0/3] EDAC: Improve memory address decoding for i10nm driver
Date: Thu, 1 Sep 2022 12:43:07 -0700 [thread overview]
Message-ID: <20220901194310.115427-1-tony.luck@intel.com> (raw)
Calling firmware to translate memory addresses has a high impact
on system because the call uses SMI.
The 10nm server processors (Icelake and Tremont) provide additional
information in the IA32_MCi_MISC registers that can be used to decode
the address of an error in DDR memory.
Couple of prep patches before the main event in part 3 that decodes
the address from the MISC register.
Qiuxu Zhuo (2):
EDAC/skx_common: Use driver decoder first
EDAC/skx_common: Make output format similar
Youquan Song (1):
EDAC/i10nm: Add driver decoder for Ice Lake and Tremont CPUs
arch/x86/include/asm/mce.h | 1 +
drivers/edac/skx_common.h | 6 ++
drivers/edac/i10nm_base.c | 134 ++++++++++++++++++++++++++++++++++++-
drivers/edac/skx_base.c | 9 ++-
drivers/edac/skx_common.c | 21 +++---
5 files changed, 158 insertions(+), 13 deletions(-)
base-commit: b90cb1053190353cc30f0fef0ef1f378ccc063c5
--
2.37.1
next reply other threads:[~2022-09-01 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 19:43 Tony Luck [this message]
2022-09-01 19:43 ` [PATCH 1/3] EDAC/skx_common: Use driver decoder first Tony Luck
2022-09-01 19:43 ` [PATCH 2/3] EDAC/skx_common: Make output format similar Tony Luck
2022-09-01 19:43 ` [PATCH 3/3] EDAC/i10nm: Add driver decoder for Ice Lake and Tremont CPUs Tony Luck
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=20220901194310.115427-1-tony.luck@intel.com \
--to=tony.luck@intel.com \
--cc=aris@redhat.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=patches@lists.linux.dev \
--cc=qiuxu.zhuo@intel.com \
--cc=youquan.song@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