From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
tony.luck@intel.com, x86@kernel.org,
Smita.KoralahalliChannabasappa@amd.com
Subject: Re: [PATCH] x86/MCE/AMD: Allow thresholding interface updates after init
Date: Mon, 17 Jan 2022 15:14:52 +0000 [thread overview]
Message-ID: <YeWH7EEGXo5CyvoU@yaz-ubuntu> (raw)
In-Reply-To: <Ycyd+nYgXvJpL19y@zn.tnic>
On Wed, Dec 29, 2021 at 06:42:18PM +0100, Borislav Petkov wrote:
> On Tue, Dec 07, 2021 at 07:30:28PM +0000, Yazen Ghannam wrote:
> > Changes to the AMD Thresholding sysfs code prevents sysfs writes from
> > updating the underlying registers once CPU init is completed, i.e.
> > "threshold_banks" is set.
> >
> > Allow the registers to be updated if the thresholding interface is
> > already initialized or if in the init path. Use the "set_lvt_off" value
> > to indicate if running in the init path, since this value is only set
> > during init.
> >
> > Fixes: a037f3ca0ea0 ("x86/mce/amd: Make threshold bank setting hotplug robust")
> > Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
>
> We want that in stable, right?
>
Yes, thanks for catching that.
> > ---
> > arch/x86/kernel/cpu/mce/amd.c | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/x86/kernel/cpu/mce/amd.c b/arch/x86/kernel/cpu/mce/amd.c
> > index 2eadc7c4c902..408c9546ea0b 100644
> > --- a/arch/x86/kernel/cpu/mce/amd.c
> > +++ b/arch/x86/kernel/cpu/mce/amd.c
> > @@ -400,8 +400,12 @@ static void threshold_restart_bank(void *_tr)
> > struct thresh_restart *tr = _tr;
> > u32 hi, lo;
> >
> > - /* sysfs write might race against an offline operation */
> > - if (this_cpu_read(threshold_banks))
> > + /*
> > + * sysfs write might race against an offline operation.
> > + * Prevent register writes if threshold_banks are not set and this is
> > + * not called from the init path as indicated by "set_lvt_off".
> > + */
>
> So if you convert this text into code, it would read like:
>
> if (!this_cpu_read(threshold_banks) && !tr->set_lvt_off)
>
> which is equivalent to:
>
> > + if (!(this_cpu_read(threshold_banks) || tr->set_lvt_off))
>
> but easier to follow, methinks.
>
Sure, I'll make the change and send another version.
Thanks,
Yazen
prev parent reply other threads:[~2022-01-17 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 19:30 [PATCH] x86/MCE/AMD: Allow thresholding interface updates after init Yazen Ghannam
2021-12-29 17:42 ` Borislav Petkov
2022-01-17 15:14 ` Yazen Ghannam [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=YeWH7EEGXo5CyvoU@yaz-ubuntu \
--to=yazen.ghannam@amd.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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