From: Borislav Petkov <bp@alien8.de>
To: Tony Luck <tony.luck@intel.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Marco Elver <elver@google.com>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] x86/mce: Fix more noinstr fun
Date: Fri, 4 Feb 2022 09:30:12 +0100 [thread overview]
Message-ID: <20220204083015.17317-1-bp@alien8.de> (raw)
From: Borislav Petkov <bp@suse.de>
Hi all,
here's a second small set of fixes for objtool noinstr validation issues
in the MCE code.
It goes ontop of tip:locking/core where there are some more commits
changing generic helpers to be always inlined.
As always, comments and suggestions are appreciated.
Thx.
Borislav Petkov (3):
cpumask: Add a x86-specific cpumask_clear_cpu() helper
x86/ptrace: Always inline v8086_mode() for instrumentation
x86/mce: Use arch atomic and bit helpers
arch/x86/include/asm/cpumask.h | 10 ++++++
arch/x86/include/asm/ptrace.h | 2 +-
arch/x86/kernel/cpu/mce/core.c | 58 ++++++++++--------------------
arch/x86/kernel/cpu/mce/internal.h | 23 ++++++++++--
arch/x86/kernel/cpu/mce/severity.c | 2 +-
include/linux/cpumask.h | 4 +--
6 files changed, 54 insertions(+), 45 deletions(-)
--
2.29.2
next reply other threads:[~2022-02-04 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 8:30 Borislav Petkov [this message]
2022-02-04 8:30 ` [PATCH 1/3] cpumask: Add a x86-specific cpumask_clear_cpu() helper Borislav Petkov
2022-02-04 16:46 ` Luck, Tony
2022-02-04 18:04 ` Borislav Petkov
2022-02-13 10:59 ` [tip: locking/core] " tip-bot2 for Borislav Petkov
2022-02-04 8:30 ` [PATCH 2/3] x86/ptrace: Always inline v8086_mode() for instrumentation Borislav Petkov
2022-02-13 10:59 ` [tip: locking/core] " tip-bot2 for Borislav Petkov
2022-02-04 8:30 ` [PATCH 3/3] x86/mce: Use arch atomic and bit helpers Borislav Petkov
2022-02-14 10:03 ` [tip: ras/core] " tip-bot2 for Borislav Petkov
2022-02-04 11:24 ` [PATCH 0/3] x86/mce: Fix more noinstr fun Marco Elver
2022-02-04 14:48 ` 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=20220204083015.17317-1-bp@alien8.de \
--to=bp@alien8.de \
--cc=elver@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--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