From: Manfred Spraul <manfred@colorfullife.com>
To: Akira Tsukamoto <at541@columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Performance improvement with Akira Tsukamoto's Athlon copy_user patch
Date: Tue, 19 Nov 2002 20:18:25 +0100 [thread overview]
Message-ID: <3DDA8E81.4070508@colorfullife.com> (raw)
>I read the code of laze FPU state saving and confirmed that
>if the function does not generate exception than
>'kernel_fpu_begin/end()' should assure fpu safe inside kernel.
>
>However, it is not enough where exception could rise, as Takahashi
>mentioned.
I had prototyped an exception safe kfpu framework, but then I didn't have the time to submit/cleanup it.
http://www.colorfullife.com/~manfred/linux-2.5/sse/patch-kfpu
Have you tried SSE based copy_to_user? With SSE, you can just save the affected registers, without unexpected sideeffects.
--
Manfred
next reply other threads:[~2002-11-19 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 19:18 Manfred Spraul [this message]
2002-11-20 6:03 ` Performance improvement with Akira Tsukamoto's Athlon copy_user patch Akira Tsukamoto
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 17:34 szonyi calin
2002-11-19 18:20 ` Akira Tsukamoto
2002-11-19 18:23 ` Akira Tsukamoto
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=3DDA8E81.4070508@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=at541@columbia.edu \
--cc=linux-kernel@vger.kernel.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