All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 0/2] CR4 fixes (one is urgent)
Date: Thu, 29 Sep 2016 12:48:10 -0700	[thread overview]
Message-ID: <cover.1475178369.git.luto@kernel.org> (raw)

Hi Ingo, etc:

Patch 1 fixes a boot regressions that's new in 4.8.

Patch 2 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 patch 1 to x86/urgent, merge into x86/asm,
and apply patch 3 on top.

Changes from v1:
 - Drop the patch that was already applied.
 - Get rid of pointless CPUID check, which simplifies it a bit (Borislav)

Andy Lutomirski (2):
  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/include/asm/tlbflush.h       |  2 +-
 arch/x86/kernel/paravirt.c            |  1 -
 arch/x86/kernel/process_32.c          |  2 +-
 arch/x86/kernel/setup.c               |  4 +---
 arch/x86/power/cpu.c                  |  2 +-
 arch/x86/xen/enlighten.c              |  1 -
 9 files changed, 11 insertions(+), 28 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-09-29 19:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 19:48 Andy Lutomirski [this message]
2016-09-29 19:48 ` [PATCH v2 1/2] x86/boot: Fix another __read_cr4() case on 486 Andy Lutomirski
2016-09-29 22:38   ` Borislav Petkov
2016-09-30 10:43   ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2016-09-29 19:48 ` [PATCH v2 2/2] x86/asm: Get rid of __read_cr4_safe() Andy Lutomirski
2016-09-30 10:45   ` [tip:x86/asm] " tip-bot for 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.1475178369.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.