linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] RAS changes for v5.3
Date: Mon, 8 Jul 2019 11:51:02 +0200	[thread overview]
Message-ID: <20190708095102.GA59026@gmail.com> (raw)

Linus,

Please pull the latest ras-core-for-linus git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-core-for-linus

   # HEAD: 6e4f929ea8b2097b0052f6674de839a3c9d477e9 x86/mce: Do not check return value of debugfs_create functions

Boris is on vacation so I'm sending the RAS bits this time. The main 
changes were:

 - Various RAS/CEC improvements and fixes by Borislav Petkov:
    - error insertion fixes
    - offlining latency fix
    - memory leak fix
    - additional sanity checks
    - cleanups
    - debug output improvements

 - More SMCA enhancements by Yazen Ghannam:
 
    - make banks truly per-CPU which they are in the hardware,
    - don't over-cache certain registers, 
    - make the number of MCA banks per-CPU variable.

   The long term goal with these changes is to support future 
   heterogenous SMCA extensions.

 - Misc fixes and improvements.

 Thanks,

	Ingo

------------------>
Borislav Petkov (8):
      RAS/CEC: Fix pfn insertion
      RAS/CEC: Check count_threshold unconditionally
      RAS/CEC: Do not set decay value on error
      RAS/CEC: Fix potential memory leak
      RAS/CEC: Sanity-check array on every insertion
      RAS/CEC: Rename count_threshold to action_threshold
      RAS/CEC: Dump the different array element sections
      RAS/CEC: Add copyright

Greg Kroah-Hartman (1):
      x86/mce: Do not check return value of debugfs_create functions

Tony Luck (1):
      RAS/CEC: Add CONFIG_RAS_CEC_DEBUG and move CEC debug features there

Yazen Ghannam (5):
      x86/MCE: Make struct mce_banks[] static
      x86/MCE: Make mce_banks a per-CPU array
      x86/MCE/AMD: Don't cache block addresses on SMCA systems
      x86/MCE: Make the number of MCA banks a per-CPU variable
      x86/MCE: Determine MCA banks' init state properly


 arch/x86/kernel/cpu/mce/amd.c      |  92 +++++++++----------
 arch/x86/kernel/cpu/mce/core.c     | 177 +++++++++++++++++++++++++------------
 arch/x86/kernel/cpu/mce/inject.c   |  37 ++------
 arch/x86/kernel/cpu/mce/internal.h |  12 +--
 arch/x86/kernel/cpu/mce/severity.c |  14 +--
 arch/x86/ras/Kconfig               |  10 +++
 drivers/ras/cec.c                  | 132 ++++++++++++++++-----------
 7 files changed, 269 insertions(+), 205 deletions(-)

             reply	other threads:[~2019-07-08  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08  9:51 Ingo Molnar [this message]
2019-07-09  1:45 ` [GIT PULL] RAS changes for v5.3 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=20190708095102.GA59026@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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).