From: Borislav Petkov <bp@alien8.de>
To: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: tony.luck@intel.com, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org, avadhut.naik@amd.com,
john.allen@amd.com, Muralidhara M K <muralidhara.mk@amd.com>
Subject: Re: [PATCH] RAS/AMD/ATL: Add MI300 support
Date: Mon, 29 Jan 2024 10:25:41 +0100 [thread overview]
Message-ID: <20240129092541.GAZbdvFbXrdpENB97h@fat_crate.local> (raw)
In-Reply-To: <20240128155950.1434067-1-yazen.ghannam@amd.com>
On Sun, Jan 28, 2024 at 09:59:50AM -0600, Yazen Ghannam wrote:
> From: Muralidhara M K <muralidhara.mk@amd.com>
>
> AMD MI300 systems include on-die HBM3 memory and a unique topology. And
> they fall under Data Fabric version 4.5 in overall design.
>
> Generally, topology information (IDs, etc.) is gathered from Data Fabric
> registers. However, the unique topology for MI300 means that some
> topology information is fixed in hardware and follows arbitrary
> mappings. Furthermore, not all hardware instances are software-visible,
> so register accesses must be adjusted.
>
> Recognize and add helper functions for the new MI300 interleave modes.
> Add lookup tables for fixed values where appropriate. Adjust how Die and
> Node IDs are found and used.
>
> Also, fix some register bitmasks that were mislabeled.
>
> Signed-off-by: Muralidhara M K <muralidhara.mk@amd.com>
> Co-developed-by: Yazen Ghannam <yazen.ghannam@amd.com>
> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
Applied, thanks.
> ---
> Notes:
> This patch is based on patches 2, 4, and 5 from the following set.
> https://lore.kernel.org/r/20231129073521.2127403-1-muralimk@amd.com
>
> Patch 3 from above set is still needed for complete MI300 address
> translation support. This will be the first to follow.
>
> Patch 6 from above set is needed for expanding page retirement on MI300
> systems. This will be the second to follow.
>
> Patch 1 from above set adds MI200 support to ATL. This will be deferred
> until after priority MI300 updates.
Yap, agreed.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2024-01-29 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 15:59 Yazen Ghannam
2024-01-29 9:25 ` Borislav Petkov [this message]
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=20240129092541.GAZbdvFbXrdpENB97h@fat_crate.local \
--to=bp@alien8.de \
--cc=avadhut.naik@amd.com \
--cc=john.allen@amd.com \
--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
all inboxes | Powered by JetHome®