mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	bp@alien8.de, linux-edac@vger.kernel.org
Cc: yazen.ghannam@amd.com, linux-kernel@vger.kernel.org,
	avadhut.naik@amd.com, tony.luck@intel.com, john.allen@amd.com,
	william.roche@oracle.com, muralidhara.mk@amd.com
Subject: Re: [PATCH v4 1/3] RAS: Introduce AMD Address Translation Library
Date: Mon, 18 Dec 2023 16:53:24 -0500	[thread overview]
Message-ID: <2f114c41-5dbb-4019-b0f1-046509521d44@amd.com> (raw)
In-Reply-To: <42c6ed78-75bd-4b4b-8b59-e0562d4968aa@wanadoo.fr>

On 12/18/2023 2:21 PM, Christophe JAILLET wrote:
> Le 18/12/2023 à 20:04, Yazen Ghannam a écrit :
>> AMD Zen-based systems report memory errors through Machine Check banks
>> representing Unified Memory Controllers (UMCs). The address value
>> reported for DRAM ECC errors is a "normalized address" that is relative
>> to the UMC. This normalized address must be converted to a system
>> physical address to be usable by the OS.
>>
>> Support for this address translation was introduced to the MCA subsystem
>> with Zen1 systems. The code was later moved to the AMD64 EDAC module,
>> since this was the only user of the code at the time.
>>
>> However, there are uses for this translation outside of EDAC. The system
>> physical address can be used in MCA for preemptive page offlining as done
>> in some MCA notifier functions. Also, this translation is needed as the
>> basis of similar functionality needed for some CXL configurations on AMD
>> systems.
>>
>> Introduce a common address translation library that can be used for
>> multiple subsystems including MCA, EDAC, and CXL.
>>
>> Include support for UMC normalized to system physical address
>> translation for current CPU systems.
>>
>> The Data Fabric Indirect register access offsets and one of the register
>> fields were changed. Default to the current offsets and register field
>> definition. And fallback to the older values if running on a "legacy"
>> system.
>>
>> Provide built-in code to facilitate the loading and unloading of the
>> library module without affecting other modules or built-in code.
>>
>> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
>> ---
> 
> ...
> 
>> +int get_address_map(struct addr_ctx *ctx)
>> +{
>> +    int ret = 0;
> 
> Nit: unneeded init
> 
>> +
>> +    ret = get_address_map_common(ctx);
>> +    if (ret)
>> +        goto out;
>> +
>> +    ret = get_global_map_data(ctx);
>> +    if (ret)
>> +        goto out;
>> +
>> +    dump_address_map(&ctx->map);
>> +
>> +out:
>> +    return ret;
>> +}
>> diff --git a/drivers/ras/amd/atl/reg_fields.h 
>> b/drivers/ras/amd/atl/reg_fields.h
>> new file mode 100644
>> index 000000000000..6aaa5093f42c
>> --- /dev/null
>> +++ b/drivers/ras/amd/atl/reg_fields.h
>> @@ -0,0 +1,603 @@
> 
> ...
> 
>> +static void get_num_maps(void)
>> +{
>> +    switch (df_cfg.rev) {
>> +    case DF2:
>> +    case DF3:
>> +    case DF3p5:
>> +        df_cfg.num_coh_st_maps    = 2;
>> +        break;
>> +    case DF4:
>> +        df_cfg.num_coh_st_maps    = 4;
>> +        break;
> 
> If 4 is the correct value in both cases, DF4 and DF4p5 cases could be 
> merged.
> 
> CJ
> 
>> +    case DF4p5:
>> +        df_cfg.num_coh_st_maps    = 4;
>> +        break;
>> +    default:
>> +        atl_debug_on_bad_df_rev();
>> +    }
>> +}
> 
> ...
> 

Yep, good points. Thanks for your feedback!

-Yazen

  reply	other threads:[~2023-12-18 21:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 19:04 [PATCH v4 0/3] " Yazen Ghannam
2023-12-18 19:04 ` [PATCH v4 1/3] RAS: Introduce " Yazen Ghannam
2023-12-18 19:21   ` Christophe JAILLET
2023-12-18 21:53     ` Yazen Ghannam [this message]
2023-12-19 16:07       ` Borislav Petkov
2023-12-19 16:39   ` Borislav Petkov
2023-12-19 16:57   ` Borislav Petkov
2023-12-20 15:45   ` Markus Elfring
2023-12-20 16:15   ` Markus Elfring
2023-12-20 17:28   ` Markus Elfring
2023-12-28 17:16   ` Borislav Petkov
2024-01-03 11:36   ` [tip: ras/core] " tip-bot2 for Yazen Ghannam
2023-12-18 19:04 ` [PATCH v4 2/3] EDAC/amd64: Use new " Yazen Ghannam
2024-01-03 11:36   ` [tip: ras/core] " tip-bot2 for Yazen Ghannam
2023-12-18 19:04 ` [PATCH v4 3/3] Documentation: RAS: Add index and address translation section Yazen Ghannam
2024-01-03 11:36   ` [tip: ras/core] " tip-bot2 for Yazen Ghannam
2024-01-03 10:59 ` [PATCH v4 0/3] AMD Address Translation Library 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=2f114c41-5dbb-4019-b0f1-046509521d44@amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=avadhut.naik@amd.com \
    --cc=bp@alien8.de \
    --cc=christophe.jaillet@wanadoo.fr \
    --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=william.roche@oracle.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®