From: Kim Phillips <kim.phillips@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add support for FP emulation for the e300c2 core
Date: Wed, 22 Nov 2006 16:09:57 -0600 [thread overview]
Message-ID: <20061122160957.5b516c65.kim.phillips@freescale.com> (raw)
In-Reply-To: <1164231274.5653.28.camel@localhost.localdomain>
On Thu, 23 Nov 2006 08:34:34 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > +BEGIN_FTR_SECTION
> > +/*
> > + * certain freescale cores treat 'normal' floating point instructions
> > + * as FP Unavail exception. Redirect to normal illegal/emulation handling.
> > + */
> > + b ProgramCheck
> > +END_FTR_SECTION_IFSET(CPU_FTR_FP_TAKES_FPUNAVAIL)
> > EXCEPTION_PROLOG
> > bne load_up_fpu /* if from user, just load it up */
> > addi r3,r1,STACK_FRAME_OVERHEAD
>
> Do you absolutely need that ? Is there any way those cores will actually
The feature section provides a means of distinguishing among other processors (i.e. those with FPUs) at runtime.
> send a "normal" FPUnavail exception ? If not, don't bother. There aren't
no, it never takes the Illegal instruction/ProgramCheck exception by itself when a FP insn is in the pipe.
> that many CPU feature bits left so let's not use one for something that
> never happens.
>
this happens when executing a binary with FP instructions compiled in. This feature will be reused when support for other FPUless core variants coming from freescale are added.
Kim
next prev parent reply other threads:[~2006-11-22 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 20:20 [PATCH] Add support for FP emulation for the e300c2 core Kim Phillips
2006-11-22 21:34 ` Benjamin Herrenschmidt
2006-11-22 22:09 ` Kim Phillips [this message]
2006-12-04 3:23 ` Paul Mackerras
2006-12-04 4:41 ` Kumar Gala
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=20061122160957.5b516c65.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).