All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>, Jean-Frederic <jfgaudreault@gmail.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [GIT PULL] EDAC pile for 5.4 -> AMD family 17h, model 70h support
Date: Thu, 10 Oct 2019 19:00:18 +0000	[thread overview]
Message-ID: <60b68d6c-5aff-3e7c-9461-c26a5f28cd87@amd.com> (raw)
In-Reply-To: <20191010134128.GF7658@zn.tnic>

On 10/10/2019 9:41 AM, Borislav Petkov wrote:
> On Thu, Oct 10, 2019 at 08:48:20AM -0400, Jean-Frederic wrote:
>> I did recheck all menus in advanced mode several times. I used my bios
>> fairly often when I got this new system, I would also have seen it
>> before I would think.
> 
> I have the faint suspicion that our perfectly capable BIOS writers
> forgot to add a disable functionality. Let's see what Yazen finds out
> first, though.
> 

I believe PFEH is generally geared towards enterprise users which is why I
remembered it once you mentioned your system is EPYC. I don't really know if
it's being used for desktop/client systems. Of course, it's up to the vendor
which features they choose to implement. I haven't seen it in the client
documentation though.

There's no explicit way to check if PFEH is enabled from the kernel. The
feature is meant to be transparent to the OS.

However, MCA_MISC0 will be Read-as-Zero/Writes-Ignored for all MCA banks when
PFEH is enabled. So you can use this as an implicit check. This is just an
implementation detail though for current systems. It's not an architectural
requirement.

Jean-Frederic,
Please do the following if you'd like to try this check:
1) rdmsr 0xC0002003

This command will read the MCA_MISC0 register from MCA bank 0. If it is
non-zero, then we'll know that PFEH is not enabled.

The "rdmsr" command is usually found in the msr-tools package in many distros.
You will need to run it as root, and you may need to load the "msr" module
before using the command.

Thanks,
Yazen

  reply	other threads:[~2019-10-10 19:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEVokG7TeAbmkhaxiTpsxhv1pQzqRpU=mR8gVjixb5kXo3s2Eg@mail.gmail.com>
     [not found] ` <20190924092644.GC19317@zn.tnic>
2019-10-05 16:52   ` [GIT PULL] EDAC pile for 5.4 -> AMD family 17h, model 70h support Jeff God
2019-10-07  7:16     ` Borislav Petkov
2019-10-07 12:58       ` Jeff God
2019-10-08 11:50         ` Borislav Petkov
2019-10-08 19:42           ` Ghannam, Yazen
2019-10-08 23:08             ` Jeff God
2019-10-09 10:30               ` Borislav Petkov
2019-10-09 20:31                 ` Ghannam, Yazen
2019-10-09 23:54                   ` Jeff God
2019-10-10  9:56                     ` Borislav Petkov
2019-10-10 12:48                       ` Jean-Frederic
2019-10-10 13:41                         ` Borislav Petkov
2019-10-10 19:00                           ` Ghannam, Yazen [this message]
2019-10-11  1:04                             ` Jean-Frederic
2019-10-18 23:08                               ` Jean-Frederic
2019-10-19  8:25                                 ` Borislav Petkov
2019-10-19 16:12                                   ` Jean-Frederic
2019-10-21 14:24                                     ` Ghannam, Yazen
2020-01-04 20:03                                     ` Jean-Frederic
2020-01-04 21:47                                       ` Jean-Frederic
2019-10-10  9:54                   ` 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=60b68d6c-5aff-3e7c-9461-c26a5f28cd87@amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=bp@alien8.de \
    --cc=jfgaudreault@gmail.com \
    --cc=linux-edac@vger.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 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.