From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>, Rik van Riel <riel@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] x86/FPU updates
Date: Thu, 19 Feb 2015 11:20:48 +0100 [thread overview]
Message-ID: <20150219102048.GA765@gmail.com> (raw)
In-Reply-To: <20150219084001.GB31218@pd.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> Hi guys,
>
> please pull, thanks.
>
> ---
> The following changes since commit bfa76d49576599a4b9f9b7a71f23d73d6dcff735:
>
> Linux 3.19 (2015-02-08 18:54:22 -0800)
>
> 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 b8938491e4fcc668cf803de1bf4c224b3fa6a0ad:
>
> x86, fpu: Also check fpu_lazy_restore when use_eager_fpu (2015-02-17 18:58:34 +0100)
>
> ----------------------------------------------------------------
> A round of updates to the FPU maze from Oleg and Rik. It should make the
> code a bit more understandable/readable/streamlined and a preparation
> for more cleanups and improvements in that area.
>
> ----------------------------------------------------------------
> Oleg Nesterov (3):
> x86, fpu, unlazy_fpu: Don't reset thread.fpu_counter
> x86, fpu: unlazy_fpu: don't do __thread_fpu_end() if use_eager_fpu()
> x86, fpu: Kill save_init_fpu(), change math_error() to use unlazy_fpu()
>
> Rik van Riel (5):
> x86, fpu: Move lazy restore functions up a few lines
> x86, fpu: Introduce task_disable_lazy_fpu_restore helper
> x86, fpu: Use an explicit if/else in switch_fpu_prepare
> x86, fpu: Use task_disable_lazy_fpu_restore() helper
> x86, fpu: Also check fpu_lazy_restore when use_eager_fpu
>
> arch/x86/include/asm/fpu-internal.h | 82 ++++++++++++++++++-------------------
> arch/x86/kernel/i387.c | 13 +++---
> arch/x86/kernel/process.c | 2 +-
> arch/x86/kernel/traps.c | 2 +-
> 4 files changed, 49 insertions(+), 50 deletions(-)
Pulled into tip:x86/fpu, thanks a lot!
Ingo
next prev parent reply other threads:[~2015-02-19 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 8:40 [GIT PULL] x86/FPU updates Borislav Petkov
2015-02-19 10:20 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-02 20:13 [GIT PULL] x86/fpu updates Borislav Petkov
2015-03-03 11:14 ` 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=20150219102048.GA765@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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