From: Tony Luck <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Tony Luck <tony.luck@intel.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Aristeu Rozanski <aris@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-edac@vger.kernel.org
Subject: [PATCH 0/2] Fix i10nm_edac driver load failure
Date: Fri, 24 Apr 2020 11:57:36 -0700 [thread overview]
Message-ID: <20200424185738.7985-1-tony.luck@intel.com> (raw)
The root cause is that one of the configuration registers
needed by EDAC changed offset between pre-production and
final stepping of some CPU models. Ordinarily we might fix
this by just making the driver only support the production
stepping. But there are still significant numbers of the
pre-production parts in use (both within Intel and with
customers), so we need to adapt to use the right offset
for the register depending on both model and stepping.
Patch 1: Adds a configuration structure to make this, and future
changes, possible.
Patch 2: Adjusts the register offset
Qiuxu Zhuo (2):
EDAC, {skx,i10nm}: Make some configurations CPU model specific
EDAC, i10nm: Fix i10nm_edac loading failure on some servers
drivers/edac/i10nm_base.c | 28 ++++++++++++++++++++++++----
drivers/edac/skx_base.c | 12 ++++++++++--
drivers/edac/skx_common.c | 11 +++++------
drivers/edac/skx_common.h | 11 +++++++++--
4 files changed, 48 insertions(+), 14 deletions(-)
--
2.21.1
next reply other threads:[~2020-04-24 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 18:57 Tony Luck [this message]
2020-04-24 18:57 ` [PATCH 1/2] EDAC, {skx,i10nm}: Make some configurations CPU model specific Tony Luck
2020-04-27 8:32 ` Borislav Petkov
2020-04-24 18:57 ` [PATCH 2/2] EDAC, i10nm: Fix i10nm_edac loading failure on some servers Tony Luck
2020-04-27 8:40 ` Borislav Petkov
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=20200424185738.7985-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=mchehab@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).