From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ras/core for v6.2
Date: Mon, 12 Dec 2022 21:05:39 +0100 [thread overview]
Message-ID: <Y5eJk3Tqh3Ip3oCx@zn.tnic> (raw)
Hi Linus,
please pull some updates to the RAS side of things, for 6.2.
Thx.
---
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/ras_core_for_v6.2
for you to fetch changes up to 50865c14f34edbd03f8113147fac069b39f4e390:
RAS: Fix return value from show_trace() (2022-10-31 18:55:18 +0100)
----------------------------------------------------------------
- Fix confusing output from /sys/kernel/debug/ras/daemon_active
- Add another MCE severity error case to the Intel error severity
table to promote UC and AR errors to panic severity and remove the
corresponding code condition doing that.
- Make sure the thresholding and deferred error interrupts on AMD SMCA
systems clear the all registers reporting an error so that there are no
multiple errors logged for the same event
----------------------------------------------------------------
Tony Luck (2):
x86/mce: Use severity table to handle uncorrected errors in kernel
RAS: Fix return value from show_trace()
Yazen Ghannam (1):
x86/MCE/AMD: Clear DFR errors found in THR handler
arch/x86/kernel/cpu/mce/amd.c | 33 ++++++++++++++++++++-------------
arch/x86/kernel/cpu/mce/severity.c | 8 +++++---
drivers/ras/debugfs.c | 2 +-
3 files changed, 26 insertions(+), 17 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2022-12-12 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 20:05 Borislav Petkov [this message]
2022-12-12 23:45 ` pr-tracker-bot
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=Y5eJk3Tqh3Ip3oCx@zn.tnic \
--to=bp@alien8.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
all inboxes | Powered by JetHome®