From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: x86/RAS updates for 5.7
Date: Mon, 30 Mar 2020 10:56:09 +0200 [thread overview]
Message-ID: <20200330085554.GD14624@zn.tnic> (raw)
Hi Linus,
please pull the RAS updates which got collected this time around.
Thx.
---
The following changes since commit 11a48a5a18c63fd7621bb050228cebf13566e4d8:
Linux 5.6-rc2 (2020-02-16 13:16:59 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/ras_updates_for_5.7
for you to fetch changes up to 077168e241ec5a3b273652acb1e85f8bc1dc2d81:
x86/mce/amd: Add PPIN support for AMD MCE (2020-03-22 11:03:47 +0100)
----------------------------------------------------------------
* Do not report spurious MCEs on some Intel platforms caused by errata;
by Prarit Bhargava.
* Change dev-mcelog's hardcoded limit of 32 error records to a dynamic
one, controlled by the number of logical CPUs, by Tony Luck.
* Add support for the processor identification number (PPIN) on AMD, by
Wei Huang.
----------------------------------------------------------------
Prarit Bhargava (1):
x86/mce: Do not log spurious corrected mce errors
Tony Luck (1):
x86/mce/dev-mcelog: Dynamically allocate space for machine check records
Wei Huang (1):
x86/mce/amd: Add PPIN support for AMD MCE
arch/x86/include/asm/cpufeatures.h | 1 +
arch/x86/include/asm/mce.h | 6 ++---
arch/x86/kernel/cpu/amd.c | 30 +++++++++++++++++++++++
arch/x86/kernel/cpu/mce/core.c | 4 +++
arch/x86/kernel/cpu/mce/dev-mcelog.c | 47 +++++++++++++++++++++---------------
arch/x86/kernel/cpu/mce/intel.c | 17 +++++++++++++
arch/x86/kernel/cpu/mce/internal.h | 2 ++
7 files changed, 84 insertions(+), 23 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
reply other threads:[~2020-03-30 8:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200330085554.GD14624@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).