xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: "Luis R. Rodriguez" <mcgrof-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: lguest-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
	Andrew Cooper
	<andrew.cooper3-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>,
	x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
	Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>,
	david.vrabel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org,
	Andy Lutomirski <luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	boris.ostrovsky-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org
Subject: [PATCH 0/2] x86/entry/32: Get rid of paravirt_enabled in ESPFIX
Date: Mon, 29 Feb 2016 15:45:22 -0800	[thread overview]
Message-ID: <cover.1456789300.git.luto@kernel.org> (raw)

Hi Luis-

As promised, here are these patches.

Borislav, if you're okay with this (ab)use of the cpufeatures stuff
and if they survive review, I'd be okay with them joining your
series or going straight into tip:x86/asm.

Andy Lutomirski (2):
  x86/nmi/64: Giant debugging hack
  x86/entry/32: Introduce and use X86_BUG_ESPFIX instead of
    paravirt_enabled

 arch/x86/entry/entry_32.S          | 15 ++-------------
 arch/x86/entry/entry_64.S          | 34 ++++++++++++++++++++++++++++++----
 arch/x86/include/asm/cpufeatures.h |  8 ++++++++
 arch/x86/include/asm/segment.h     |  5 ++++-
 arch/x86/kernel/cpu/common.c       | 27 +++++++++++++++++++++++++++
 5 files changed, 71 insertions(+), 18 deletions(-)

-- 
2.5.0

_______________________________________________
Lguest mailing list
Lguest@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/lguest

             reply	other threads:[~2016-02-29 23:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 23:45 Andy Lutomirski [this message]
     [not found] ` <cover.1456789157.git.luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
     [not found]   ` <cover.1456789300.git.luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-02-29 23:45     ` [PATCH 1/2] x86/entry/32: Introduce and use X86_BUG_ESPFIX instead of paravirt_enabled Andy Lutomirski
2016-02-29 23:45     ` [PATCH 1/2] x86/nmi/64: Giant debugging hack Andy Lutomirski
2016-02-29 23:45     ` [PATCH 2/2] x86/asm-offsets: Remove PARAVIRT_enabled Andy Lutomirski
2016-02-29 23:45     ` [PATCH 2/2] x86/entry/32: Introduce and use X86_BUG_ESPFIX instead of paravirt_enabled 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.1456789300.git.luto@kernel.org \
    --to=luto-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=andrew.cooper3-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
    --cc=boris.ostrovsky-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
    --cc=david.vrabel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
    --cc=konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=lguest-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=mcgrof-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.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).