From: Jun Sun <jsun@mvista.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ralf Baechle <ralf@uni-koblenz.de>,
linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: [patch] linux: New style IRQs for DECstation
Date: Mon, 08 Apr 2002 11:25:54 -0700 [thread overview]
Message-ID: <3CB1E0B2.8020707@mvista.com> (raw)
In-Reply-To: Pine.GSO.3.96.1020408195036.26107N-100000@delta.ds2.pg.gda.pl
Maciej W. Rozycki wrote:
> On Mon, 8 Apr 2002, Jun Sun wrote:
>
>
>>What is the intention of introducing MIPS_CPU_FPUEX? It seems an overkill if
>>it is just needed by DecStation. How many CPUs really need this?
>>
>
> It's needed by any system using a (logically) external FPU. If set it
> means there is no need to install a special FPU exception handler using a
> general-purpose interrupt line. It's a generic flag.
>
> Even if it's only of limited use now, it is not an excuse for not writing
> clean code. I'm afraid the current mess within the MIPS port is a result
> of people trying to think locally and I'm trying to avoid it. Are there
> any trade-offs of this flags you see and I don't? I'm willing to change
> the code if there really are.
>
Generally interrupt dispatching belongs to machine/board-specific code. So I
think FPU exeption through an interrupt is probably best handled within DEC's
code, instead of being generalized to the common code.
In addition, conceptional you might have a system where FPU exception is
handled through an interrupt and yet CPU has FPU exception.
Of course abstraction and generalization can happen later when it becomes
obvious. It is just not obvious, at least to me.
Jun
next prev parent reply other threads:[~2002-04-08 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 17:04 [patch] linux: New style IRQs for DECstation Maciej W. Rozycki
2002-04-08 17:48 ` Jun Sun
2002-04-08 18:03 ` Maciej W. Rozycki
2002-04-08 18:25 ` Jun Sun [this message]
2002-04-09 14:41 ` Maciej W. Rozycki
2002-04-09 17:36 ` Jun Sun
2002-04-10 13:31 ` Maciej W. Rozycki
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=3CB1E0B2.8020707@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@uni-koblenz.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 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.