From: Gareth Hughes <gareth@precisioninsight.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Kettenis <kettenis@wins.uva.nl>,
drepper@redhat.com, adam@yggdrasil.com,
linux-kernel@vger.rutgers.edu, bug-glibc@gnu.org,
gdb@sourceware.cygnus.com
Subject: Re: [PATCH] Updates to FXSR/SSE support in 2.4.0-test1
Date: Sat, 10 Jun 2000 18:14:00 -0000 [thread overview]
Message-ID: <3943C920.3F7E39B1@precisioninsight.com> (raw)
In-Reply-To: <E130vpf-0000pI-00@the-village.bc.nu>
Alan Cox wrote:
>
> > What happens when a signal occurs in a time slice where the application
> > hasn't used the FPU? Having the regular FPU environment around means we
>
> You touch the FPU, it loads the FPU state you save both. If the FPU state
> is already loaded it costs nothing. The FNSAVE stuff is horribly slow so
> it is a real concern.
I'm not sure I understand what you're advocating here. If you're okay
with converting the FXSAVE data back and forth, then so am I.
> > I'll play around with the conversion into/out of the signal handler and
> > GETFPREGS request. Should only take a short while, so don't do anything
> > with the stuff I sent out yesterday.
>
> Right now its correct, this is about being correct clean and fast so we are
> going the right way
I certainly agree with making it clean and fast, as well as correct.
Would you prefer the conversion and just using FXSAVE/FXRSTOR?
-- Gareth
next prev parent reply other threads:[~2000-06-10 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3942529D.A848DFBE@precisioninsight.com>
2000-06-09 19:51 ` Gareth Hughes
2000-06-10 17:26 ` Mark Kettenis
2000-06-10 17:41 ` Gareth Hughes
2000-06-10 17:47 ` Alan Cox
2000-06-10 18:14 ` Gareth Hughes [this message]
2000-06-10 18:44 ` Alan Cox
2000-06-11 1:03 ` [PATCH] More updates " Gareth Hughes
2000-06-11 17:03 ` Mark Kettenis
2000-06-11 21:56 ` Gareth Hughes
2000-06-12 13:59 ` Mark Kettenis
2000-06-19 20:56 ` Gareth Hughes
2000-06-20 10:43 ` Jim Blandy
2000-06-14 15:48 ` Jim Blandy
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=3943C920.3F7E39B1@precisioninsight.com \
--to=gareth@precisioninsight.com \
--cc=adam@yggdrasil.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bug-glibc@gnu.org \
--cc=drepper@redhat.com \
--cc=gdb@sourceware.cygnus.com \
--cc=kettenis@wins.uva.nl \
--cc=linux-kernel@vger.rutgers.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).