[PATCH v7 0/3] Incorporate DRAM address in EDAC messages

Yazen Ghannam <[email protected]>
Newsgroups org.kernel.vger.linux-edac,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
Hi all,

This revision includes a new pre-patch based on the diff from Boris in
the last revision. The subsequent patches were fixed up as needed. There
were some minor changes due to formatting, etc. Boris, please do adjust
the attributions as you see fit.

The first patch has an Assisted-by tag due to help spotting and fixing a
build issue with a particular Kconfig combination.

Thanks,
Yazen

Cc: Avadhut Naik <[email protected]>

Link:
https://lore.kernel.org/[email protected]

Changes in v7:
- Drop fake_inject patch that was already accepted.
- Remove function pointers. (Boris).

Changes in v6:
- Remove fake_inject interface. (Boris)
- Add two more values to 'other_detail'.

Changes in v5:
 - Address a comment from Sashiko in patch 2.

Changes in v4:
 - Drop a "handler available" check in patch 1.
 - Reword commit message in patch 2.
 - Reformat string in patch 2.

Avadhut Naik (2):
  RAS/AMD/ATL: Translate UMC normalized address to DRAM address using
    PRM
  EDAC/amd64: Include DRAM address in output

Yazen Ghannam (1):
  RAS/AMD/ATL: Directly export address translation helper

 drivers/edac/amd64_edac.c      | 34 ++++++++++++++++++++++++++++++++--
 drivers/edac/amd64_edac.h      |  3 +++
 drivers/ras/amd/atl/core.c     | 23 ++++++++++++-----------
 drivers/ras/amd/atl/internal.h | 11 ++++++++++-
 drivers/ras/amd/atl/prm.c      | 32 ++++++++++++++++++++++++++++----
 drivers/ras/amd/atl/system.c   |  3 +++
 drivers/ras/amd/atl/umc.c      | 11 ++++++++++-
 drivers/ras/amd/fmpm.c         |  2 +-
 drivers/ras/ras.c              | 31 -------------------------------
 include/linux/ras.h            | 22 +++++++++++++++++-----
 10 files changed, 116 insertions(+), 56 deletions(-)


base-commit: 1129f95c19e50823398822a775c9adc141113196
-- 
2.53.0
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.