From: Avi Kivity <avi@redhat.com>
To: George Spelvin <linux@horizon.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, npiggin@suse.de
Subject: Re: [PATCH 0/4] Really lazy fpu
Date: Wed, 16 Jun 2010 14:46:52 +0300 [thread overview]
Message-ID: <4C18B9AC.3070409@redhat.com> (raw)
In-Reply-To: <20100616113253.24017.qmail@science.horizon.com>
On 06/16/2010 02:32 PM, George Spelvin wrote:
>
> (An halfway version of this optimization whoch sould avoid the need for
> an IPI would be *save* the FPU state, but mark it "clean", so the re-load
> can be skipped if we're lucky. If the code supported this as well as the
> IPI alternative, you could make a heuristic guess at switch-out time
> whether to save immediately or hope the odds of needing the IPI are less than
> the fxsave/IPI cost ratio.)
>
That's an interesting optimization - and we already have something
similar in the form of fpu preload. Shouldn't be too hard to do.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-16 11:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 11:32 [PATCH 0/4] Really lazy fpu George Spelvin
2010-06-16 11:46 ` Avi Kivity [this message]
2010-06-17 9:38 ` George Spelvin
-- strict thread matches above, loose matches on Subject: below --
2010-06-13 15:03 Avi Kivity
2010-06-13 20:45 ` Valdis.Kletnieks
2010-06-14 7:47 ` Avi Kivity
2010-06-16 7:24 ` Avi Kivity
2010-06-16 7:32 ` H. Peter Anvin
2010-06-16 8:02 ` Avi Kivity
2010-06-16 8:39 ` Ingo Molnar
2010-06-16 9:01 ` Samuel Thibault
2010-06-16 9:43 ` Avi Kivity
2010-06-16 9:10 ` Nick Piggin
2010-06-16 9:30 ` Avi Kivity
2010-06-16 9:28 ` Avi Kivity
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=4C18B9AC.3070409@redhat.com \
--to=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
/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).