mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: yazen.ghannam@amd.com, tony.luck@intel.com,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	avadhut.naik@amd.com, john.allen@amd.com, muralidhara.mk@amd.com,
	naveenkrishna.chatradhi@amd.com, sathyapriya.k@amd.com
Subject: Re: [PATCH 2/2] RAS: Introduce the FRU Memory Poison Manager
Date: Wed, 14 Feb 2024 09:56:14 -0500	[thread overview]
Message-ID: <3f793ed7-b65c-48d0-a556-f51bdf4f5add@amd.com> (raw)
In-Reply-To: <20240214110541.GFZcyehY44eSSYsW2l@fat_crate.local>

On 2/14/2024 6:05 AM, Borislav Petkov wrote:
> On Tue, Feb 13, 2024 at 09:35:16PM -0600, Yazen Ghannam wrote:
>> +static inline struct cper_fru_poison_desc *get_fpd(struct fru_rec *rec, u32 entry)
>> +{
>> +	return &rec->entries[entry];
>> +}
> 
> This one needs to go too.
>

Ack.
  
>> +static inline u32 get_fmp_len(struct fru_rec *rec)
>> +{
>> +	return rec->sec_desc.section_length - sizeof(struct cper_section_descriptor);
>> +}
> 
> Oh well, I guess we can keep that one.
>

Okay.
  
>> +/* Calculate a new checksum. */
>> +static u32 get_fmp_checksum(struct fru_rec *rec)
>> +{
>> +	struct cper_sec_fru_mem_poison *fmp = get_fmp(rec);
>> +	u32 len, checksum;
>> +
>> +	len = get_fmp_len(rec);
>> +
>> +	/* Get the current total. */
>> +	checksum = do_fmp_checksum(fmp, len);
>> +
>> +	/* Subtract the current checksum from total. */
>> +	checksum -= fmp->checksum;
>> +
>> +	/* Return the compliment value. */
>> +	return 0 - checksum;
>> +}
> 
> Let's get rid of that one.
> 
> Also, I think it is called *complement* value and you simply do
>

Yep, good catch! (compliment)
  
>          /* Use the complement value. */
>          rec->fmp.checksum = -checksum;
> 
> I'd say.
>

This was my first thought. Other checksum code in the kernel does
the (0-X) thing. So I wasn't sure if there's any odd side effects
of one over the other. And I didn't take the time to dig into it.
  
> ---
> 
> diff --git a/drivers/ras/amd/fmpm.c b/drivers/ras/amd/fmpm.c
> index 9eaf892e35b9..f8799beddcc4 100644
> --- a/drivers/ras/amd/fmpm.c
> +++ b/drivers/ras/amd/fmpm.c
> @@ -195,11 +195,12 @@ static u32 do_fmp_checksum(struct cper_sec_fru_mem_poison *fmp, u32 len)
>   	return checksum;
>   }
>   
> -/* Calculate a new checksum. */
> -static u32 get_fmp_checksum(struct fru_rec *rec)

I made this a helper because we need to validate the checksum when
reading records from storage too.

> +static int update_record_on_storage(struct fru_rec *rec)
>   {
>   	u32 len, checksum;
> +	int ret;
>   
> +	/* Calculate a new checksum. */
>   	len = get_fmp_len(rec);
>   
>   	/* Get the current total. */
> @@ -208,15 +209,8 @@ static u32 get_fmp_checksum(struct fru_rec *rec)
>   	/* Subtract the current checksum from total. */
>   	checksum -= rec->fmp.checksum;
>   
> -	/* Return the compliment value. */
> -	return 0 - checksum;
> -}
> -
> -static int update_record_on_storage(struct fru_rec *rec)
> -{
> -	int ret;
> -
> -	rec->fmp.checksum = get_fmp_checksum(rec);
> +	/* Use the complement value. */
> +	rec->fmp.checksum = -checksum;
>   
>   	pr_debug("Writing to storage");
>   
> 

Thanks,
Yazen

  reply	other threads:[~2024-02-14 14:56 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  3:35 [PATCH 0/2] " Yazen Ghannam
2024-02-14  3:35 ` [PATCH 1/2] RAS/AMD/ATL, EDAC/amd64: Move MI300 Row Retirement to ATL Yazen Ghannam
2024-02-14  8:36   ` Borislav Petkov
2024-02-14 14:19     ` Yazen Ghannam
2024-02-14 16:05       ` Borislav Petkov
2024-02-14  3:35 ` [PATCH 2/2] RAS: Introduce the FRU Memory Poison Manager Yazen Ghannam
2024-02-14  9:06   ` Borislav Petkov
2024-02-14 14:21     ` Yazen Ghannam
2024-02-14 15:49       ` Borislav Petkov
2024-02-14 16:01         ` Yazen Ghannam
2024-02-14 16:11           ` Borislav Petkov
2024-02-14  9:28   ` Borislav Petkov
2024-02-14 14:28     ` Yazen Ghannam
2024-02-14 17:50       ` Borislav Petkov
2024-02-14 18:21         ` Borislav Petkov
2024-02-14 10:29   ` Borislav Petkov
2024-02-14 14:45     ` Yazen Ghannam
2024-02-14 18:04       ` Borislav Petkov
2024-02-14 10:34   ` Borislav Petkov
2024-02-14 14:46     ` Yazen Ghannam
2024-02-14 18:29       ` Borislav Petkov
2024-02-14 10:51   ` Borislav Petkov
2024-02-14 14:49     ` Yazen Ghannam
2024-02-14 11:05   ` Borislav Petkov
2024-02-14 14:56     ` Yazen Ghannam [this message]
2024-02-14 18:44       ` Borislav Petkov
2024-02-14 11:10   ` Borislav Petkov
2024-02-14 14:57     ` Yazen Ghannam
2024-02-14 11:15   ` Borislav Petkov
2024-02-14 14:59     ` Yazen Ghannam
2024-02-14 11:36   ` Borislav Petkov
2024-02-14 15:26     ` Yazen Ghannam
2024-02-14 19:44       ` Borislav Petkov
2024-02-14 20:10       ` Borislav Petkov
2024-02-14 12:02   ` Borislav Petkov
2024-02-14 15:33     ` Yazen Ghannam
2024-02-14 20:18       ` Borislav Petkov
2024-02-14 18:47   ` Borislav Petkov
2024-02-14  7:52 ` [PATCH 0/2] " Borislav Petkov
2024-02-20 12:29   ` M K, Muralidhara
2024-02-20 17:10     ` M K, Muralidhara

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=3f793ed7-b65c-48d0-a556-f51bdf4f5add@amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=avadhut.naik@amd.com \
    --cc=bp@alien8.de \
    --cc=john.allen@amd.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muralidhara.mk@amd.com \
    --cc=naveenkrishna.chatradhi@amd.com \
    --cc=sathyapriya.k@amd.com \
    --cc=tony.luck@intel.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®