From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: david@saggiorato.net, Borislav Petkov <bp@alien8.de>,
Brian Gerst <brgerst@gmail.com>,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/3] CR4 fixes (some are urgent)
Date: Wed, 28 Sep 2016 12:34:13 -0700 [thread overview]
Message-ID: <cover.1475091074.git.luto@kernel.org> (raw)
Hi Ingo, etc:
Patches 1 and 2 fix boot regressions. Patch 1 needs to be
backported. Patch 2 doesn't because the regression is new in 4.8
(although it's probably unobservable because the regression fixed in
patch 1 also prevented bootup on affected CPUs).
Patch 3 cleans the whole mess up. It's probably not 4.8 material,
but I'm sending it as part of this series for ease of review. If
you like, you could apply patches 1 and 2 to x86/urgent, merge into
x86/asm, and apply patch 3 on top.
Andy Lutomirski (3):
x86/init: Fix cr4_init_shadow() on CR4-less machines
x86/boot: Fix another __read_cr4() case on 486
x86/asm: Get rid of __read_cr4_safe()
arch/x86/include/asm/paravirt.h | 4 ----
arch/x86/include/asm/paravirt_types.h | 1 -
arch/x86/include/asm/special_insns.h | 22 +++++++---------------
arch/x86/kernel/paravirt.c | 1 -
arch/x86/kernel/process_32.c | 2 +-
arch/x86/kernel/setup.c | 9 +++++++--
arch/x86/power/cpu.c | 2 +-
arch/x86/xen/enlighten.c | 1 -
8 files changed, 16 insertions(+), 26 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-28 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 19:34 Andy Lutomirski [this message]
2016-09-28 19:34 ` [PATCH 1/3] x86/init: Fix cr4_init_shadow() on CR4-less machines Andy Lutomirski
2016-09-29 11:44 ` Borislav Petkov
2016-09-29 18:21 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2016-09-28 19:34 ` [PATCH 2/3] x86/boot: Fix another __read_cr4() case on 486 Andy Lutomirski
2016-09-29 11:48 ` Borislav Petkov
2016-09-29 19:09 ` Andy Lutomirski
2016-09-28 19:34 ` [PATCH 3/3] x86/asm: Get rid of __read_cr4_safe() Andy Lutomirski
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=cover.1475091074.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=david@saggiorato.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).