From: Ralf Baechle <ralf@linux-mips.org>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: when does do_fpe() get called? (or when does FPE happen?)
Date: Tue, 28 Jan 2003 18:45:29 +0100 [thread overview]
Message-ID: <20030128184529.B29262@linux-mips.org> (raw)
In-Reply-To: <20030128093742.V11633@mvista.com>; from jsun@mvista.com on Tue, Jan 28, 2003 at 09:37:42AM -0800
On Tue, Jan 28, 2003 at 09:37:42AM -0800, Jun Sun wrote:
> > > Can someone enlighten me a little? I am trying
> > > to figure out what the FPU state should be (or can be) when
> > > we are inside do_fpe() routine.
> >
> > Checkout the various flags in $fcr31. Whenever one of the enabled
> > exceptions is triggered we get to handle_fpe via do_fpe. In addition
> > the unimplemented exception can also result in invocation of do_fpe.
> >
>
> So it seems safe to assume FPU should have been enabled when we get
> here, right?
Yes, otherwise we'd get a coprocessur unusable exception.
Ralf
prev parent reply other threads:[~2003-01-28 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 3:04 when does do_fpe() get called? (or when does FPE happen?) Jun Sun
2003-01-28 3:37 ` Ralf Baechle
2003-01-28 17:37 ` Jun Sun
2003-01-28 17:45 ` Ralf Baechle [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=20030128184529.B29262@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.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