From: Kumar Gala <kumar.gala@freescale.com>
To: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Jason McMullan <jason.mcmullan@timesys.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Kumar Gala <galak@freescale.com>,
linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] ppc32: refactor FPU exception handling
Date: Tue, 12 Apr 2005 00:42:36 -0500 [thread overview]
Message-ID: <f54dd3f8af3f508dc7774fb841a8877a@freescale.com> (raw)
In-Reply-To: <1113272915.5388.37.camel@gaston>
Ben,
Sorry about that, we have had some back and forth on this on the ppc=20
embedded list.
Not sure I understand your concern about the duplication of the fast=20
exception return path? Jason's patch pretty much just moved code out=20
of head.S into fpu.S so we dont duplicate it between head.S and=20
head_44x.S & head_fsl_booke.S
- kumar
On Apr 11, 2005, at 9:28 PM, Benjamin Herrenschmidt wrote:
> On Mon, 2005-04-11 at 17:02 -0500, Kumar Gala wrote:
> > Andrew,
> >
> > Moved common FPU exception handling code out of head.S so it can be=20=
> used
> > by several of the sub-architectures that might of a full PowerPC=20
> FPU.=A0
> >
> > Also, uses new CONFIG_PPC_FPU define to fix alignment exception
> > handling for floating point load/store instructions to only occur if=20=
> we
> > have a hardware FPU.
> >
> > Signed-off-by: Jason McMullan <jason.mcmullan@timesys.com>
> > Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
>
>
>
> Andrew, please hold on this patch, it hasn't been properly discussed
> with the relevant maintainer, that is Paul Mackerras.
>
> I can see matter for debate in there, like the whole duplication of =
the
> fast exception return path...
>
> It's also touching quite sensitive bits of kernel code (head.S) that
> needs careful auditing and testing before beeing pushed upstream.
>
> Ben.
next prev parent reply other threads:[~2005-04-12 5:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 22:02 [PATCH] ppc32: refactor FPU exception handling Kumar Gala
2005-04-12 2:28 ` Benjamin Herrenschmidt
2005-04-12 5:42 ` Kumar Gala [this message]
2005-04-12 14:59 ` Kumar Gala
2005-04-19 14:49 ` Kumar Gala
2005-04-20 0:17 ` Paul Mackerras
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=f54dd3f8af3f508dc7774fb841a8877a@freescale.com \
--to=kumar.gala@freescale.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=galak@freescale.com \
--cc=jason.mcmullan@timesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@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).