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, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: [GIT PULL] x86/fpu changes for v5.1
Date: Thu, 7 Mar 2019 19:39:05 +0100	[thread overview]
Message-ID: <20190307183905.GA85249@gmail.com> (raw)

Linus,

Please pull the latest x86-fpu-for-linus git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-fpu-for-linus

   # HEAD: 2f7726f955572e587d5f50fbe9b2deed5334bd90 x86/fpu: Track AVX-512 usage of tasks

Three changes:

 - There's a preparatory patches for AVX state tracking that 
   computing-cluster folks would like to use for user-space batching - 
   but we are not happy about the related ABI yet so this is only the 
   kernel tracking side.

 - There's a cleanup for CR0 handling in do_device_not_available().

 - Plus we removed a workaround for an ancient binutils version.

 Thanks,

	Ingo

------------------>
Aubrey Li (1):
      x86/fpu: Track AVX-512 usage of tasks

Borislav Petkov (2):
      x86/traps: Have read_cr0() only once in the #NM handler
      x86/fpu: Get rid of CONFIG_AS_FXSAVEQ


 arch/x86/Makefile                   |  1 -
 arch/x86/include/asm/fpu/internal.h | 57 +++++++++----------------------------
 arch/x86/include/asm/fpu/types.h    |  7 +++++
 arch/x86/kernel/traps.c             |  5 ++--
 4 files changed, 22 insertions(+), 48 deletions(-)


             reply	other threads:[~2019-03-07 18:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 18:39 Ingo Molnar [this message]
2019-03-08  2:30 ` [GIT PULL] x86/fpu changes for v5.1 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=20190307183905.GA85249@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).