From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Avi Kivity <avi@redhat.com>
Cc: "Cui, Dexuan" <dexuan.cui@intel.com>,
Sheng Yang <sheng@linux.intel.com>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86: Introduce 'struct fpu' and related API
Date: Tue, 04 May 2010 11:12:31 -0700 [thread overview]
Message-ID: <1272996751.2833.10.camel@sbs-t61.sc.intel.com> (raw)
In-Reply-To: <1272812038-32484-3-git-send-email-avi@redhat.com>
On Sun, 2010-05-02 at 07:53 -0700, Avi Kivity wrote:
> Currently all fpu state access is through tsk->thread.xstate. Since we wish
> to generalize fpu access to non-task contexts, wrap the state in a new
> 'struct fpu' and convert existing access to use an fpu API.
>
> Signal frame handlers are not converted to the API since they will remain
> task context only things.
>
> Signed-off-by: Avi Kivity <avi@redhat.com>
One comment I have is the name 'fpu'. In future we can use this for non
fpu state aswell. For now, I can't think of a simple and better name. We
can perhaps change it in the future.
Acked-by: Suresh Siddha <suresh.b.siddha@intel.com>
prev parent reply other threads:[~2010-05-04 18:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 14:53 [PATCH 0/2] x86 FPU API Avi Kivity
2010-05-02 14:53 ` [PATCH 1/2] x86: eliminate TS_XSAVE Avi Kivity
2010-05-02 17:38 ` Brian Gerst
2010-05-02 17:44 ` Avi Kivity
2010-05-03 21:45 ` H. Peter Anvin
2010-05-04 7:41 ` Avi Kivity
2010-05-04 18:15 ` Suresh Siddha
2010-05-04 18:24 ` H. Peter Anvin
2010-05-05 7:30 ` Avi Kivity
2010-05-05 12:10 ` H. Peter Anvin
2010-05-05 12:12 ` H. Peter Anvin
2010-05-04 18:03 ` Suresh Siddha
2010-05-02 14:53 ` [PATCH 2/2] x86: Introduce 'struct fpu' and related API Avi Kivity
2010-05-04 18:12 ` Suresh Siddha [this message]
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=1272996751.2833.10.camel@sbs-t61.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=avi@redhat.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 \
/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