From: Jean-Frederic <jfgaudreault@gmail.com>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>, Borislav Petkov <bp@alien8.de>
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 21:04:41 -0400 [thread overview]
Message-ID: <79bca0d0-42eb-c232-6bbe-a958734e096d@gmail.com> (raw)
In-Reply-To: <60b68d6c-5aff-3e7c-9461-c26a5f28cd87@amd.com>
On 2019-10-10 3:00 p.m., Ghannam, Yazen wrote:
> Jean-Frederic,
> Please do the following if you'd like to try this check:
> 1) rdmsr 0xC0002003
This returns 0 for me, so I guess PFEH is enabled.
As long as this is only for the error injection, and is not preventing
the actual capability for the OS to report the memory errors.
I'm still not clear on that part.
> 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.
>
--
Jean-Frédéric
next prev parent reply other threads:[~2019-10-11 1:04 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
2019-10-11 1:04 ` Jean-Frederic [this message]
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=79bca0d0-42eb-c232-6bbe-a958734e096d@gmail.com \
--to=jfgaudreault@gmail.com \
--cc=Yazen.Ghannam@amd.com \
--cc=bp@alien8.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).