public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: [GIT PULL] ras/core for 6.1
Date: Tue, 4 Oct 2022 11:18:48 +0200	[thread overview]
Message-ID: <Yzv6eCHCFWFp0adu@zn.tnic> (raw)

Hi Linus,

please pull two x86 RAS improvements for 6.1.

Thx.

---

The following changes since commit 1c23f9e627a7b412978b4e852793c5e3c3efc555:

  Linux 6.0-rc2 (2022-08-21 17:32:54 -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.1_rc1

for you to fetch changes up to f9781bb18ed828e7b83b7bac4a4ad7cd497ee7d7:

  x86/mce: Retrieve poison range from hardware (2022-08-29 09:33:42 +0200)

----------------------------------------------------------------
- Fix the APEI MCE callback handler to consult the hardware about the
granularity of the memory error instead of hard-coding it

- Offline memory pages on Intel machines after 2 errors reported per page

----------------------------------------------------------------
Jane Chu (1):
      x86/mce: Retrieve poison range from hardware

Tony Luck (1):
      RAS/CEC: Reduce offline page threshold for Intel systems

 arch/x86/kernel/cpu/mce/apei.c | 13 ++++++++++++-
 drivers/ras/cec.c              |  8 ++++++++
 2 files changed, 20 insertions(+), 1 deletion(-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)

             reply	other threads:[~2022-10-04  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  9:18 Borislav Petkov [this message]
2022-10-04 17:34 ` [GIT PULL] ras/core for 6.1 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=Yzv6eCHCFWFp0adu@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