public inbox for linux-edac@vger.kernel.org
 help / color / mirror / Atom feed
From: John Allen <john.allen@amd.com>
To: <bp@alien8.de>, <linux-edac@vger.kernel.org>,
	<tony.luck@intel.com>, <yazen.ghannam@amd.com>
Cc: <linux-kernel@vger.kernel.org>, <avadhut.naik@amd.com>,
	<muralidhara.mk@amd.com>, John Allen <john.allen@amd.com>
Subject: [PATCH v5 0/6] RAS: ATL: DF 4.5 NP2 Denormalization
Date: Thu, 6 Jun 2024 20:33:07 +0000	[thread overview]
Message-ID: <20240606203313.51197-1-john.allen@amd.com> (raw)

Implement non-power-of-two denormalization for Data Fabric 4.5 in the
AMD address translation library.

Tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git
Base commit:
dadc295cbd03955cc1ba55af55e23a06713d1a5f
(origin/edac-amd-atl)

v2:
  - Fix compilation error.
  - Make remove_base_and_hole the inverse of add_base_and_hole.
  - Move all map validation checks to validate_address_map at the
    beginning of translation
v3:
  - Fix bug where the legacy hole was not getting removed properly.
  - Minor rework of functions for matching the normalized address and
    logical cs fabric id.
v4:
  - Merge common cases in map validation function.
  - Fix map validation for cases that don't have explicit checks.
v5:
  - Add patches to add a pr_fmt prefix for the driver and share the
    internal.h header with the FMPM driver.
  - Don't fail to load driver if DRAM hole base can't be read.

John Allen (6):
  RAS/AMD/ATL: Add amd_atl pr_fmt prefix
  RAS/AMD/ATL: Read DRAM hole base early
  RAS/AMD/ATL: Expand helpers for adding and removing base and hole
  RAS/AMD/ATL: Validate address map when information is gathered
  RAS/AMD/ATL: Implement DF 4.5 NP2 denormalization
  RAS/AMD/FMPM: Use atl internal.h for INVALID_SPA

 drivers/ras/amd/atl/core.c        |  50 +--
 drivers/ras/amd/atl/dehash.c      |  43 ---
 drivers/ras/amd/atl/denormalize.c | 561 ++++++++++++++++++++++++++++++
 drivers/ras/amd/atl/internal.h    |  48 +++
 drivers/ras/amd/atl/map.c         |  97 ++++++
 drivers/ras/amd/atl/system.c      |  21 +-
 drivers/ras/amd/fmpm.c            |   4 +-
 7 files changed, 755 insertions(+), 69 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-06-06 20:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 20:33 John Allen [this message]
2024-06-06 20:33 ` [PATCH v5 1/6] RAS/AMD/ATL: Add amd_atl pr_fmt prefix John Allen
2024-06-06 20:33 ` [PATCH v5 2/6] RAS/AMD/ATL: Read DRAM hole base early John Allen
2024-06-06 20:33 ` [PATCH v5 3/6] RAS/AMD/ATL: Expand helpers for adding and removing base and hole John Allen
2024-06-06 20:33 ` [PATCH v5 4/6] RAS/AMD/ATL: Validate address map when information is gathered John Allen
2024-06-06 20:33 ` [PATCH v5 5/6] RAS/AMD/ATL: Implement DF 4.5 NP2 denormalization John Allen
2024-06-06 20:33 ` [PATCH v5 6/6] RAS/AMD/FMPM: Use atl internal.h for INVALID_SPA John Allen
2024-06-10  6:23 ` [PATCH v5 0/6] RAS: ATL: DF 4.5 NP2 Denormalization 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=20240606203313.51197-1-john.allen@amd.com \
    --to=john.allen@amd.com \
    --cc=avadhut.naik@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muralidhara.mk@amd.com \
    --cc=tony.luck@intel.com \
    --cc=yazen.ghannam@amd.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