All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Allen <john.allen@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org, tony.luck@intel.com,
	yazen.ghannam@amd.com, linux-kernel@vger.kernel.org,
	avadhut.naik@amd.com, muralidhara.mk@amd.com
Subject: Re: [PATCH v4 1/4] RAS/AMD/ATL: Read DRAM hole base early
Date: Wed, 5 Jun 2024 13:47:31 -0500	[thread overview]
Message-ID: <ZmCyw4ePEl09hv5z@AUS-L1-JOHALLEN.amd.com> (raw)
In-Reply-To: <20240528081659.GDZlWS-9eT0U3_cf_V@fat_crate.local>

On Tue, May 28, 2024 at 10:16:59AM +0200, Borislav Petkov wrote:
> On Mon, May 06, 2024 at 03:46:02PM +0000, John Allen wrote:
> > @@ -282,6 +298,11 @@ int get_df_system_info(void)
> >  
> >  	get_num_maps();
> >  
> > +	if (get_dram_hole_base()) {
> > +		pr_warn("amd_atl: Failed to read DRAM hole base");
> 
> This thing with the printk prefix "amd_atl: ". Please do a pre-patch
> which adds
> 
> #undef pr_fmt
> #define pr_fmt(fmt) "amd_atl: " fmt
> 
> to ...atl/internal.h and remove all such string prefixes from the pr_*
> statements in the driver.
> 
> > +		return -EINVAL;
> 
> So this basically says that the driver won't load if it can't read hole
> base. But it did load before - on failure to read that reg, it would
> simply fail translating.
> 
> So why is that failure so tragic? Or is it that we absolutely need hole
> base in all circumstances so that loading it is pointless if not?

Yeah, I see your point now. In the case that DF_LEGACY_MMIO_HOLE_EN is
not set, the hole base will not be needed and should not be fatal. I'll
remove the EINVAL return here and check that the hole base was read
successfully before using it in cases where it is needed.

Thanks,
John

  reply	other threads:[~2024-06-05 18:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 15:46 [PATCH v4 0/4] RAS: ATL: DF 4.5 NP2 Denormalization John Allen
2024-05-06 15:46 ` [PATCH v4 1/4] RAS/AMD/ATL: Read DRAM hole base early John Allen
2024-05-28  8:16   ` Borislav Petkov
2024-06-05 18:47     ` John Allen [this message]
2024-05-06 15:46 ` [PATCH v4 2/4] RAS/AMD/ATL: Expand helpers for adding and removing base and hole John Allen
2024-05-28 10:07   ` Borislav Petkov
2024-05-06 15:46 ` [PATCH v4 3/4] RAS/AMD/ATL: Validate address map when information is gathered John Allen
2024-05-28 10:11   ` Borislav Petkov
2024-05-06 15:46 ` [PATCH v4 4/4] RAS/AMD/ATL: Implement DF 4.5 NP2 denormalization John Allen
2024-05-28 10:23   ` Borislav Petkov
2024-06-03 21:01     ` John Allen
2024-06-03 21:06       ` Borislav Petkov
2024-05-08 15:51 ` [PATCH v4 0/4] RAS: ATL: DF 4.5 NP2 Denormalization 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=ZmCyw4ePEl09hv5z@AUS-L1-JOHALLEN.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.