public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Tony Luck <tony.luck@intel.com>, Yazen Ghannam <Yazen.Ghannam@amd.com>
Cc: linux-edac <linux-edac@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] RAS: Merge mce_amd_inj into mce-inject
Date: Tue,  6 Jun 2017 11:32:46 +0200	[thread overview]
Message-ID: <20170606093250.28071-1-bp@alien8.de> (raw)

From: Borislav Petkov <bp@suse.de>

Hi,

so there's no need to have two different injectors. Also, the
mce_amd_inj interface is much more user-friendly because you can simply
write full u64 registers directly.

So merge that functionality into mce-inject. The old /dev/mcelog
functionality is still there, behind X86_MCELOG_LEGACY.

Also, the second patch removes register_mce_write_callback() and adds an
MCE injector notifier which allows us to have mce-inject be a module and
thus be able to modprobe it and remove it on a production system in case
we want to do some injecting there.

Later, we might reuse that injector notifier for other stuff if it is
deemed interesting.

Borislav Petkov (4):
  x86/mce: Merge mce_amd_inj into mce-inject
  x86/mce: Get rid of register_mce_write_callback()
  x86/mce: Cleanup include files
  x86/mce/mce-inject: Preset the MCE injection struct

 arch/x86/Kconfig                          |   2 +-
 arch/x86/Makefile                         |   2 -
 arch/x86/include/asm/mce.h                |   4 -
 arch/x86/include/asm/processor.h          |   5 +
 arch/x86/kernel/cpu/mcheck/dev-mcelog.c   |  47 ++-
 arch/x86/kernel/cpu/mcheck/mce-inject.c   | 567 +++++++++++++++++++++++++++---
 arch/x86/kernel/cpu/mcheck/mce-internal.h |   6 +-
 arch/x86/ras/Kconfig                      |  11 -
 arch/x86/ras/Makefile                     |   2 -
 arch/x86/ras/mce_amd_inj.c                | 492 --------------------------
 10 files changed, 572 insertions(+), 566 deletions(-)
 delete mode 100644 arch/x86/ras/Makefile
 delete mode 100644 arch/x86/ras/mce_amd_inj.c

-- 
2.13.0

             reply	other threads:[~2017-06-06  9:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06  9:32 Borislav Petkov [this message]
2017-06-06  9:32 ` [PATCH 1/4] x86/mce: Merge mce_amd_inj into mce-inject Borislav Petkov
2017-06-06  9:32 ` [PATCH 2/4] x86/mce: Get rid of register_mce_write_callback() Borislav Petkov
2017-06-06  9:32 ` [PATCH 3/4] x86/mce: Cleanup include files Borislav Petkov
2017-06-06  9:32 ` [PATCH 4/4] x86/mce/mce-inject: Preset the MCE injection struct Borislav Petkov
2017-06-06 13:36 ` [PATCH 0/4] RAS: Merge mce_amd_inj into mce-inject Ghannam, Yazen
2017-06-06 13:39   ` Borislav Petkov

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=20170606093250.28071-1-bp@alien8.de \
    --to=bp@alien8.de \
    --cc=Yazen.Ghannam@amd.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    /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