From: Muralidhara M K <muralimk@amd.com>
To: <linux-edac@vger.kernel.org>, <x86@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <bp@alien8.de>,
<mchehab@kernel.org>, Muralidhara M K <muralidhara.mk@amd.com>
Subject: [PATCH 0/7] Address Translation support for MI200 and MI300 models
Date: Wed, 25 Oct 2023 07:33:32 +0000 [thread overview]
Message-ID: <20231025073339.630093-1-muralimk@amd.com> (raw)
From: Muralidhara M K <muralidhara.mk@amd.com>
This patchset adds support for MI200 heterogeneous address translation support
and MI300A address translation support, fixups on HBM3 memory address maps.
The patch set depends on the Yazen's patches submitted
"AMD Address Translation Library"
https://lore.kernel.org/linux-edac/20231005173526.42831-1-yazen.ghannam@amd.com/T/#m4a9ddb63b334f367219ab0002a9a133e891f6aac
The patchset does following
Patch 1:
MI200 heterogeneous address translation support.
Patch 2:
MI300 heterogeneous address translation support.
Patch 3:
Convert HBM3 MCA Decoded address to Normalized address.
Patch 4:
lookup table to get the correct cs instance id for HBM3.
Patch 5:
Convert physical cs id to logical cs id by static lookup
table.
Patch 6:
Reading correct bit fields to get cs_fabric_id.
Patch 7:
Identify all physical pages in a row to retire all 8 columns
of pages when the error is injected to avoid future errors.
Muralidhara M K (7):
RAS: Add Address Translation support for MI200
RAS: Add Address Translation support for MI300
RAS: Add MCA Error address conversion for UMC
RAS: Add static lookup table to get CS physical ID
RAS: Add fixed Physical to logical CS ID mapping table
RAS: Get CS fabirc ID register bit fields
EDAC/amd64: RAS: platform/x86/amd: Identify all physical pages in row
drivers/edac/amd64_edac.c | 5 +
drivers/ras/amd/atl/core.c | 5 +-
drivers/ras/amd/atl/dehash.c | 149 ++++++++++++++
drivers/ras/amd/atl/denormalize.c | 110 ++++++++++-
drivers/ras/amd/atl/internal.h | 27 ++-
drivers/ras/amd/atl/map.c | 158 ++++++++++++---
drivers/ras/amd/atl/reg_fields.h | 42 +++-
drivers/ras/amd/atl/system.c | 4 +
drivers/ras/amd/atl/umc.c | 309 +++++++++++++++++++++++++++++-
include/linux/amd-atl.h | 2 +
10 files changed, 778 insertions(+), 33 deletions(-)
--
2.25.1
next reply other threads:[~2023-10-25 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 7:33 Muralidhara M K [this message]
2023-10-25 7:33 ` [PATCH 1/7] RAS: Add Address Translation support for MI200 Muralidhara M K
2023-10-26 8:44 ` kernel test robot
2023-10-25 7:33 ` [PATCH 2/7] RAS: Add Address Translation support for MI300 Muralidhara M K
2023-10-25 7:33 ` [PATCH 3/7] RAS: Add MCA Error address conversion for UMC Muralidhara M K
2023-10-25 7:33 ` [PATCH 4/7] RAS: Add static lookup table to get CS physical ID Muralidhara M K
2023-10-25 7:33 ` [PATCH 5/7] RAS: Add fixed Physical to logical CS ID mapping table Muralidhara M K
2023-10-25 7:33 ` [PATCH 6/7] RAS: Get CS fabirc ID register bit fields Muralidhara M K
2023-10-26 13:55 ` Yazen Ghannam
2023-10-25 7:33 ` [PATCH 7/7] EDAC/amd64: RAS: platform/x86/amd: Identify all physical pages in row Muralidhara M K
2023-10-26 14:31 ` Yazen Ghannam
2023-10-26 13:21 ` [PATCH 0/7] Address Translation support for MI200 and MI300 models Yazen Ghannam
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=20231025073339.630093-1-muralimk@amd.com \
--to=muralimk@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=muralidhara.mk@amd.com \
--cc=x86@kernel.org \
/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