From: Avi Kivity <avi@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Brian Gerst <brgerst@gmail.com>,
Dexuan Cui <dexuan.cui@intel.com>,
Sheng Yang <sheng@linux.intel.com>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: [PATCH v3 0/2] x86 FPU API
Date: Thu, 6 May 2010 11:45:44 +0300 [thread overview]
Message-ID: <1273135546-29690-1-git-send-email-avi@redhat.com> (raw)
Currently all fpu accessors are wedded to task_struct. However kvm also uses
the fpu in a different context. Introduce an FPU API, and replace the
current uses with the new API.
While this patchset is oriented towards deeper changes, as a first step it
simlifies xsave for kvm.
v3:
use u8 instead of bool in asm to avoid bad code generation on older
gccs.
v2:
eliminate useless padding in use_xsave() by using a larger instruction
Avi Kivity (2):
x86: eliminate TS_XSAVE
x86: Introduce 'struct fpu' and related API
arch/x86/include/asm/i387.h | 135 +++++++++++++++++++++++++++---------
arch/x86/include/asm/processor.h | 6 ++-
arch/x86/include/asm/thread_info.h | 1 -
arch/x86/include/asm/xsave.h | 7 +-
arch/x86/kernel/cpu/common.c | 5 +-
arch/x86/kernel/i387.c | 107 ++++++++++++++---------------
arch/x86/kernel/process.c | 20 +++---
arch/x86/kernel/process_32.c | 2 +-
arch/x86/kernel/process_64.c | 2 +-
arch/x86/kernel/xsave.c | 8 +-
arch/x86/math-emu/fpu_aux.c | 6 +-
11 files changed, 181 insertions(+), 118 deletions(-)
next reply other threads:[~2010-05-06 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 8:45 Avi Kivity [this message]
2010-05-06 8:45 ` [PATCH v3 1/2] x86: eliminate TS_XSAVE Avi Kivity
2010-05-06 8:45 ` [PATCH v3 2/2] x86: Introduce 'struct fpu' and related API Avi Kivity
2010-05-10 8:48 ` [PATCH v3 0/2] x86 FPU API Avi Kivity
2010-05-10 15:24 ` H. Peter Anvin
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=1273135546-29690-1-git-send-email-avi@redhat.com \
--to=avi@redhat.com \
--cc=brgerst@gmail.com \
--cc=dexuan.cui@intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sheng@linux.intel.com \
--cc=suresh.b.siddha@intel.com \
/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).