From: Borislav Petkov <bp@alien8.de>
To: "rafal@milecki.pl" <rafal@milecki.pl>,
"clemej@gmail.com" <clemej@gmail.com>
Cc: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v4 1/2] x86/MCE: Add function to allow filtering of MCA errors
Date: Tue, 26 Mar 2019 10:28:25 +0100 [thread overview]
Message-ID: <20190326092825.GF1867@zn.tnic> (raw)
In-Reply-To: <20190325163410.171021-1-Yazen.Ghannam@amd.com>
On Mon, Mar 25, 2019 at 04:34:22PM +0000, Ghannam, Yazen wrote:
> From: Yazen Ghannam <yazen.ghannam@amd.com>
>
> Some systems may report spurious MCA errors. In general, spurious MCA
> errors may be disabled by clearing a particular bit in MCA_CTL. However,
> clearing a bit in MCA_CTL may not be recommended for some errors, so the
> only option is to ignore them.
Ok, I cleaned those up and applied them here:
https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=tip-x86-urgent-ras
Rafał, John, can you guys test them pls?
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: "rafal@milecki.pl" <rafal@milecki.pl>,
"clemej@gmail.com" <clemej@gmail.com>
Cc: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: [v4,1/2] x86/MCE: Add function to allow filtering of MCA errors
Date: Tue, 26 Mar 2019 10:28:25 +0100 [thread overview]
Message-ID: <20190326092825.GF1867@zn.tnic> (raw)
On Mon, Mar 25, 2019 at 04:34:22PM +0000, Ghannam, Yazen wrote:
> From: Yazen Ghannam <yazen.ghannam@amd.com>
>
> Some systems may report spurious MCA errors. In general, spurious MCA
> errors may be disabled by clearing a particular bit in MCA_CTL. However,
> clearing a bit in MCA_CTL may not be recommended for some errors, so the
> only option is to ignore them.
Ok, I cleaned those up and applied them here:
https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=tip-x86-urgent-ras
Rafał, John, can you guys test them pls?
Thx.
next prev parent reply other threads:[~2019-03-26 9:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 16:34 [PATCH v4 1/2] x86/MCE: Add function to allow filtering of MCA errors Ghannam, Yazen
2019-03-25 16:34 ` [v4,1/2] " Yazen Ghannam
2019-03-25 16:34 ` [PATCH v4 2/2] x86/MCE/AMD: Don't report L1 BTB MCA errors on some Family 17h models Ghannam, Yazen
2019-03-25 16:34 ` [v4,2/2] " Yazen Ghannam
2019-03-27 19:19 ` [PATCH v4 2/2] " Thomas Gleixner
2019-03-27 19:19 ` [v4,2/2] " Thomas Gleixner
2019-03-27 19:29 ` [PATCH v4 2/2] " Borislav Petkov
2019-03-27 19:29 ` [v4,2/2] " Borislav Petkov
2019-03-27 19:37 ` [PATCH v4 2/2] " Thomas Gleixner
2019-03-27 19:37 ` [v4,2/2] " Thomas Gleixner
2019-04-23 18:19 ` [tip:ras/core] x86/MCE/AMD: Don't report L1 BTB MCA errors on some family " tip-bot for Yazen Ghannam
2019-04-23 18:19 ` tip-bot for Borislav Petkov
2019-03-26 7:56 ` [PATCH v4 1/2] x86/MCE: Add function to allow filtering of MCA errors Borislav Petkov
2019-03-26 7:56 ` [v4,1/2] " Borislav Petkov
2019-03-26 11:41 ` [PATCH v4 1/2] " Ghannam, Yazen
2019-03-26 11:41 ` [v4,1/2] " Yazen Ghannam
2019-03-26 15:47 ` [PATCH v4 1/2] " Borislav Petkov
2019-03-26 15:47 ` [v4,1/2] " Borislav Petkov
2019-03-26 9:28 ` Borislav Petkov [this message]
2019-03-26 9:28 ` Borislav Petkov
2019-04-23 18:19 ` [tip:ras/core] x86/MCE: Add an MCE-record filtering function tip-bot for 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=20190326092825.GF1867@zn.tnic \
--to=bp@alien8.de \
--cc=Yazen.Ghannam@amd.com \
--cc=clemej@gmail.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--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 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.