linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/fpu changes for v5.8
Date: Mon, 1 Jun 2020 18:54:25 +0200	[thread overview]
Message-ID: <20200601165425.GA1303742@gmail.com> (raw)

Linus,

Please pull the latest x86/fpu git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-fpu-2020-06-01

   # HEAD: 55e00fb66fd5048f4a3ee357018fd26fc527abca x86/fpu/xstate: Restore supervisor states for signal return

Most of the changes here related to 'XSAVES supervisor state' support,
which is a feature that allows kernel-only data to be automatically
saved/restored by the FPU context switching code.

CPU features that can be supported this way are Intel PT, 'PASID' and
CET features.

 Thanks,

	Ingo

------------------>
Fenghua Yu (3):
      x86/fpu/xstate: Rename validate_xstate_header() to validate_user_xstate_header()
      x86/fpu/xstate: Define new macros for supervisor and user xstates
      x86/fpu/xstate: Define new functions for clearing fpregs and xstates

Yu-cheng Yu (7):
      x86/fpu/xstate: Separate user and supervisor xfeatures mask
      x86/fpu/xstate: Introduce XSAVES supervisor states
      x86/fpu/xstate: Update sanitize_restored_xstate() for supervisor xstates
      x86/fpu/xstate: Update copy_kernel_to_xregs_err() for supervisor states
      x86/fpu: Introduce copy_supervisor_to_kernel()
      x86/fpu/xstate: Preserve supervisor states for the slow path in __fpu__restore_sig()
      x86/fpu/xstate: Restore supervisor states for signal return


 arch/x86/include/asm/fpu/internal.h |  10 +-
 arch/x86/include/asm/fpu/xstate.h   |  52 +++++++---
 arch/x86/kernel/fpu/core.c          |  53 ++++++----
 arch/x86/kernel/fpu/init.c          |   3 +-
 arch/x86/kernel/fpu/regset.c        |   2 +-
 arch/x86/kernel/fpu/signal.c        | 144 ++++++++++++++++++--------
 arch/x86/kernel/fpu/xstate.c        | 199 +++++++++++++++++++++++++++---------
 arch/x86/kernel/process.c           |   2 +-
 arch/x86/kernel/signal.c            |   2 +-
 9 files changed, 336 insertions(+), 131 deletions(-)

             reply	other threads:[~2020-06-01 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 16:54 Ingo Molnar [this message]
2020-06-01 21:55 ` [GIT PULL] x86/fpu changes for v5.8 pr-tracker-bot

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=20200601165425.GA1303742@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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).