From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Oleg Nesterov <oleg@redhat.com>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/fpu cleanups
Date: Mon, 9 Mar 2015 19:08:16 +0100 [thread overview]
Message-ID: <20150309180816.GF9234@pd.tnic> (raw)
Hi Ingo,
please pull two more cleanups to the FPU insanity from Oleg.
So this is *not* the urgent stuff - the urgent stuff will come later.
This is the unload-some-more-onto-tip stuff which can be safely queued
for 4.1 and I can forget about it here. :)
Thanks.
---
The following changes since commit ae486033b980346eb6a77240101210cb66924a91:
Merge tag 'tip_x86_fpu' of git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp into x86/fpu (2015-03-03 12:12:15 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/tip_x86_fpu_2
for you to fetch changes up to 9ed010d31f173be786f0398a64f08bb4a0300c3b:
x86/fpu: factor out memset(xstate, 0) in fpu_finit() paths (2015-03-04 11:57:46 +0100)
----------------------------------------------------------------
Two more cleanups from Oleg.
----------------------------------------------------------------
Oleg Nesterov (2):
x86/fpu: Change xstateregs_get()/set() to use ->xsave.i387 rather than ->fxsave
x86/fpu: factor out memset(xstate, 0) in fpu_finit() paths
arch/x86/include/asm/fpu-internal.h | 1 -
arch/x86/kernel/i387.c | 28 +++++++++++-----------------
2 files changed, 11 insertions(+), 18 deletions(-)
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next reply other threads:[~2015-03-09 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 18:08 Borislav Petkov [this message]
2015-03-10 6:06 ` [PATCH 1/2] x86/fpu: Change xstateregs_get()/set() to use ->xsave.i387 rather than ->fxsave Borislav Petkov
2015-03-10 6:06 ` [PATCH 2/2] x86/fpu: factor out memset(xstate, 0) in fpu_finit() paths Borislav Petkov
[not found] <CAJ_zFkJkHpU4Y8wrrZjO0VnhzUVqJfyrLmNfRsBRT29bgbDSHg@mail.gmail.com>
[not found] ` <20150301184650.GA12758@redhat.com>
[not found] ` <20150301185943.GA14318@redhat.com>
[not found] ` <20150302174818.GA16886@redhat.com>
2015-03-02 18:32 ` [PATCH 0/2] x86/fpu: minor cleanups Oleg Nesterov
2015-03-02 18:32 ` [PATCH 1/2] x86/regsets: change xstateregs_get/set to use ->xsave.i387 rather than ->fxsave Oleg Nesterov
2015-03-03 19:23 ` Rik van Riel
2015-03-04 10:30 ` Borislav Petkov
2015-03-10 10:08 ` [tip:x86/fpu] x86/fpu: Change xstateregs_get()/set() to use -> xsave.i387 " tip-bot for Oleg Nesterov
2015-03-02 18:32 ` [PATCH 2/2] x86/fpu: factor out memset(xstate, 0) in fpu_finit() paths Oleg Nesterov
2015-03-03 22:01 ` Rik van Riel
2015-03-04 11:38 ` Borislav Petkov
2015-03-10 10:08 ` [tip:x86/fpu] x86/fpu: Factor out memset(xstate, 0) in fpu_finit( ) paths tip-bot for Oleg Nesterov
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=20150309180816.GF9234@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).