From: Borislav Petkov <bp@amd64.org>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: hpa@zytor.com, mingo@kernel.org, torvalds@linux-foundation.org,
andreas.herrmann3@amd.com, bp@amd64.org, robert.richter@amd.com,
linux-kernel@vger.kernel.org,
"André Przywara" <andre.przywara@amd.com>
Subject: Re: [PATCH v2 0/5] eagerfpu patches for tip/x86/fpu
Date: Mon, 10 Sep 2012 20:16:14 +0200 [thread overview]
Message-ID: <20120910181614.GE4365@aftab.osrc.amd.com> (raw)
In-Reply-To: <1347300665-6209-1-git-send-email-suresh.b.siddha@intel.com>
On Mon, Sep 10, 2012 at 11:11:00AM -0700, Suresh Siddha wrote:
+ Andre.
> v2 version of the previous patchset https://lkml.org/lkml/2012/9/7/548
> that decouples eagerfpu into a synthetic cpuid feature.
>
> changes from v1:
> * Made "eagerfpu=" boot parameter tri-state
> * removed the cpu_has_xmm check in the fx_finit (not related to eagerfpu
> per-say, but this patchset touches that area of code).
>
> Suresh Siddha (5):
> x86, fpu: decouple non-lazy/eager fpu restore from xsave
> x86, fpu: enable eagerfpu by default for xsaveopt
> x86, fpu: move check_fpu() after alternative_instructions()
> x86, fpu: make eagerfpu= boot param tri-state
> x86, fpu: remove cpu_has_xmm check in the fx_finit()
>
> Documentation/kernel-parameters.txt | 6 ++
> arch/x86/include/asm/cpufeature.h | 3 +
> arch/x86/include/asm/fpu-internal.h | 53 ++++++++++++++------
> arch/x86/kernel/cpu/bugs.c | 7 ++-
> arch/x86/kernel/cpu/common.c | 2 -
> arch/x86/kernel/i387.c | 25 +++------
> arch/x86/kernel/process.c | 2 +-
> arch/x86/kernel/traps.c | 2 +-
> arch/x86/kernel/xsave.c | 95 ++++++++++++++++++++++++-----------
> 9 files changed, 129 insertions(+), 66 deletions(-)
>
> --
> 1.7.6.5
>
>
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2012-09-10 18:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 18:11 Suresh Siddha
2012-09-10 18:11 ` [PATCH v2 1/5] x86, fpu: decouple non-lazy/eager fpu restore from xsave Suresh Siddha
2012-09-17 19:11 ` Pavel Machek
2012-09-19 0:07 ` [tip:x86/fpu] x86, fpu: decouple non-lazy/ eager " tip-bot for Suresh Siddha
2012-09-10 18:11 ` [PATCH v2 2/5] x86, fpu: enable eagerfpu by default for xsaveopt Suresh Siddha
2012-09-19 0:08 ` [tip:x86/fpu] " tip-bot for Suresh Siddha
2012-09-10 18:11 ` [PATCH v2 3/5] x86, fpu: move check_fpu() after alternative_instructions() Suresh Siddha
2012-09-19 0:06 ` [tip:x86/fpu] x86, fpu: use non-lazy fpu restore for processors supporting xsave tip-bot for Suresh Siddha
2012-09-10 18:11 ` [PATCH v2 4/5] x86, fpu: make eagerfpu= boot param tri-state Suresh Siddha
2012-09-19 0:09 ` [tip:x86/fpu] " tip-bot for Suresh Siddha
2012-09-10 18:11 ` [PATCH v2 5/5] x86, fpu: remove cpu_has_xmm check in the fx_finit() Suresh Siddha
2012-09-19 0:10 ` [tip:x86/fpu] " tip-bot for Suresh Siddha
2012-09-10 18:16 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-24 21:12 [PATCH 0/6] x86, fpu: cleanups, introduce non-lazy FPU restore for xsave Suresh Siddha
2012-08-24 21:12 ` [PATCH 1/6] x86, fpu: drop_fpu() before restoring new state from sigframe Suresh Siddha
2012-08-24 22:13 ` [tip:x86/fpu] " tip-bot for Suresh Siddha
2012-09-19 0:01 ` tip-bot for Suresh Siddha
2012-08-24 21:12 ` [PATCH 2/6] x86, fpu: remove unnecessary user_fpu_end() in save_xstate_sig() Suresh Siddha
2012-08-24 22:14 ` [tip:x86/fpu] " tip-bot for Suresh Siddha
2012-08-26 11:30 ` [PATCH 2/6] " Borislav Petkov
2012-09-19 0:02 ` [tip:x86/fpu] " tip-bot for Suresh Siddha
2012-08-24 21:12 ` [PATCH 3/6] x86, kvm: use kernel_fpu_begin/end() in kvm_load/put_guest_fpu() Suresh Siddha
2012-08-24 22:15 ` [tip:x86/fpu] x86, kvm: use kernel_fpu_begin/end() in kvm_load/ put_guest_fpu() tip-bot for Suresh Siddha
2012-09-19 0:03 ` tip-bot for Suresh Siddha
2012-09-19 10:13 ` [PATCH 3/6] x86, kvm: use kernel_fpu_begin/end() in kvm_load/put_guest_fpu() Avi Kivity
2012-09-19 17:18 ` Suresh Siddha
2012-09-19 17:22 ` Avi Kivity
2012-09-19 17:25 ` Suresh Siddha
2012-09-20 9:31 ` Avi Kivity
2012-09-19 17:26 ` H. Peter Anvin
2012-09-20 9:36 ` Avi Kivity
2012-09-20 0:10 ` Suresh Siddha
2012-09-20 9:50 ` Avi Kivity
2012-09-20 18:01 ` Suresh Siddha
2012-09-22 0:19 ` [tip:x86/fpu] x86, kvm: fix kvm's usage of kernel_fpu_begin/end() tip-bot for Suresh Siddha
2012-08-24 21:13 ` [PATCH 4/6] x86, fpu: always use kernel_fpu_begin/end() for in-kernel FPU usage Suresh Siddha
2012-08-24 22:16 ` [tip:x86/fpu] " tip-bot for Suresh Siddha
2012-09-19 0:04 ` tip-bot for Suresh Siddha
2012-08-24 21:13 ` [PATCH 5/6] lguest, x86: handle guest TS bit for lazy/non-lazy fpu host models Suresh Siddha
2012-08-24 22:16 ` [tip:x86/fpu] lguest, x86: handle guest TS bit for lazy/ non-lazy " tip-bot for Suresh Siddha
2012-09-19 0:05 ` tip-bot for Suresh Siddha
2012-08-24 21:13 ` [PATCH 6/6] x86, fpu: use non-lazy fpu restore for processors supporting xsave Suresh Siddha
2012-08-24 22:17 ` [tip:x86/fpu] " tip-bot for Suresh Siddha
2012-08-24 21:33 ` [PATCH 0/6] x86, fpu: cleanups, introduce non-lazy FPU restore for xsave H. Peter Anvin
2012-08-25 18:34 ` Linus Torvalds
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=20120910181614.GE4365@aftab.osrc.amd.com \
--to=bp@amd64.org \
--cc=andre.przywara@amd.com \
--cc=andreas.herrmann3@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=robert.richter@amd.com \
--cc=suresh.b.siddha@intel.com \
--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
Powered by JetHome