public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: x86-ml <x86@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/fpu updates
Date: Mon, 2 Mar 2015 21:13:59 +0100	[thread overview]
Message-ID: <20150302201359.GL17521@pd.tnic> (raw)

Hi guys,

those three are ontop of current tip/x86/fpu; please pull,

thanks.

The following changes since commit f353e612304ba752d6b613dc02eae8116cd3e27b:

  Merge branch 'tip-x86-fpu' of git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp into x86/fpu (2015-02-19 11:19:05 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/tip_x86_fpu

for you to fetch changes up to 110d7f7513bbb916b8654da9e2973ac5bed929a9:

  x86/fpu: Don't abuse FPU in kernel threads if use_eager_fpu() (2015-02-23 15:50:45 +0100)

----------------------------------------------------------------
Three more cleanups/improvements to the FPU handling code. (Oleg Nesterov)

----------------------------------------------------------------
Oleg Nesterov (3):
      x86/fpu: __kernel_fpu_begin() should clear fpu_owner_task even if use_eager_fpu()
      x86/fpu: Always allow FPU in interrupt if use_eager_fpu()
      x86/fpu: Don't abuse FPU in kernel threads if use_eager_fpu()

 arch/x86/kernel/i387.c    | 11 ++++++-----
 arch/x86/kernel/process.c |  7 +++++++
 arch/x86/kernel/xsave.c   | 13 +------------
 3 files changed, 14 insertions(+), 17 deletions(-)

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

             reply	other threads:[~2015-03-02 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 20:13 Borislav Petkov [this message]
2015-03-03 11:14 ` [GIT PULL] x86/fpu updates Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2015-02-19  8:40 [GIT PULL] x86/FPU updates Borislav Petkov
2015-02-19 10:20 ` Ingo Molnar

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=20150302201359.GL17521@pd.tnic \
    --to=bp@alien8.de \
    --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