From: Jun Sun <jsun@mvista.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: "Kevin D. Kissell" <kevink@mips.com>, linux-mips@oss.sgi.com
Subject: Re: config option vs. run-time detection (the debate continues ...)
Date: Fri, 09 Feb 2001 11:59:18 -0800 [thread overview]
Message-ID: <3A844C16.DD53E7E0@mvista.com> (raw)
In-Reply-To: Pine.GSO.3.96.1010209123643.4645B-100000@delta.ds2.pg.gda.pl
"Maciej W. Rozycki" wrote:
>
> But the code that needs to know whether there is a real FPU present is
> indeed minimal (as it should be) thus the gain from removing the detection
> altogether in favour to a config option is at least questionable if not
> insane.
>
Do you like run-time detection better because it allows a kernel to run on
CPUs both with a FPU and without a FPU? Or there is something else to it?
Another question. I know with mips32 and mips64 we can do run-time detection
reliably. What about other existing processors?
Jun
next prev parent reply other threads:[~2001-02-09 20:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 20:27 config option vs. run-time detection (the debate continues ...) Jun Sun
2001-02-08 22:06 ` Kevin D. Kissell
2001-02-08 22:06 ` Kevin D. Kissell
2001-02-08 22:58 ` Jun Sun
2001-02-09 0:25 ` Kevin D. Kissell
2001-02-09 0:25 ` Kevin D. Kissell
2001-02-09 11:48 ` Maciej W. Rozycki
2001-02-09 12:56 ` Kevin D. Kissell
2001-02-09 12:56 ` Kevin D. Kissell
2001-02-09 13:06 ` Maciej W. Rozycki
2001-02-09 19:59 ` Jun Sun [this message]
2001-02-09 20:39 ` Maciej W. Rozycki
2001-02-09 21:31 ` Jun Sun
2001-02-10 9:01 ` Maciej W. Rozycki
2001-02-12 18:21 ` Jun Sun
2001-02-13 18:31 ` Maciej W. Rozycki
2001-02-09 22:12 ` Kevin D. Kissell
2001-02-09 22:12 ` Kevin D. Kissell
2001-02-10 9:05 ` Maciej W. Rozycki
2001-02-09 19:58 ` Florian Lohoff
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=3A844C16.DD53E7E0@mvista.com \
--to=jsun@mvista.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.