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>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: [PATCH 0/4] EDAC/intel: Some Intel EDAC driver updates
Date: Fri, 22 Jul 2022 16:33:34 -0700 [thread overview]
Message-ID: <20220722233338.341567-1-tony.luck@intel.com> (raw)
Patch 1&2 add printing of retry_rd_log registers for the HBM (high
bandwidth memory) on Sapphire Rapids CPUs.
Patch 3 prints from an extra set of retry_rd_log registers on Sapphire
Rapids.
Patch 4 adds sub-DIMM decode (bank, row, column) for Broadwell CPUs
When community review is complete, plan is to add to RAS tree after
v5.20-rc1 comes out for the v5.21 (v6.0?) merge window.
Qiuxu Zhuo (3):
EDAC/skx_common: Add ChipSelect ADXL component
EDAC/i10nm: Retrieve and print retry_rd_err_log registers for HBM
EDAC/i10nm: Print an extra register set of retry_rd_err_log
Youquan Song (1):
x86/sb_edac: Add row column translation for Broadwell
drivers/edac/skx_common.h | 10 +++
drivers/edac/i10nm_base.c | 153 ++++++++++++++++++++++++++++++++------
drivers/edac/sb_edac.c | 148 +++++++++++++++++++++++++++++++++---
drivers/edac/skx_common.c | 5 ++
4 files changed, 284 insertions(+), 32 deletions(-)
base-commit: 32346491ddf24599decca06190ebca03ff9de7f8
--
2.35.3
next reply other threads:[~2022-07-22 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 23:33 Tony Luck [this message]
2022-07-22 23:33 ` [PATCH 1/4] EDAC/skx_common: Add ChipSelect ADXL component Tony Luck
2022-07-22 23:33 ` [PATCH 2/4] EDAC/i10nm: Retrieve and print retry_rd_err_log registers for HBM Tony Luck
2022-07-22 23:33 ` [PATCH 3/4] EDAC/i10nm: Print an extra register set of retry_rd_err_log Tony Luck
2022-07-22 23:33 ` [PATCH 4/4] x86/sb_edac: Add row column translation for Broadwell 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=20220722233338.341567-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 \
/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
all inboxes | Powered by JetHome®