From: George Anzinger <george@mvista.com>
To: Andi Kleen <ak@suse.de>
Cc: david <sector2@ihug.co.nz>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: fpu now a must in kernel
Date: Thu, 09 Nov 2000 10:00:51 -0800 [thread overview]
Message-ID: <3A0AE653.70D91891@mvista.com> (raw)
In-Reply-To: <3A09E161.ACB11253@ihug.co.nz> <20001109153648.A21769@gruyere.muc.suse.de>
Andi Kleen wrote:
>
> On Thu, Nov 09, 2000 at 12:27:29PM +1300, david wrote:
> >
> > 2 . put the save / restore code in my code (NOT! GOOD! i do not wont to
> > do it this way it is not the right way)
>
> It is the right way because it only penalizes your code, not everybody else.
>
This is a MAJOR drag on preemptability. MUCH better to keep it out of
the kernel. Barring that, since context switch does not (and should
not) save/restore fp state, the using code must be preemption locked.
Sound folks won't like this.
Maybe you could explain why you think you need this and the community
here could suggest an alternative way to do the same or better.
By the way, since the kernel is not yet preemptable, you could use empty
macros to lock preemption. This way, when preemption comes (2.5) your
code will be easily found.
George
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-09 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 23:27 fpu now a must in kernel david
2000-11-08 18:46 ` Reto Baettig
2000-11-09 0:45 ` David Lang
2000-11-08 23:39 ` Timur Tabi
2000-11-09 14:36 ` Andi Kleen
2000-11-09 18:00 ` George Anzinger [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=3A0AE653.70D91891@mvista.com \
--to=george@mvista.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sector2@ihug.co.nz \
/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