From: Scott Wood <scottwood@freescale•com>
To: Mihai Caraman <mihai.caraman@freescale•com>
Cc: linuxppc-dev@lists•ozlabs.org, Alexander Graf <agraf@suse•de>,
kvm-ppc@vger•kernel.org
Subject: Re: [PATCH v2 1/2] powerpc/booke: Restrict SPE exception handlers to e200/e500 cores
Date: Wed, 20 Aug 2014 20:57:23 -0500 [thread overview]
Message-ID: <1408586243.4058.96.camel@snotra.buserror.net> (raw)
In-Reply-To: <1408540144-24436-1-git-send-email-mihai.caraman@freescale.com>
On Wed, 2014-08-20 at 16:09 +0300, Mihai Caraman wrote:
> SPE exception handlers are now defined for 32-bit e500mc cores even though
> SPE unit is not present and CONFIG_SPE is undefined.
>
> Restrict SPE exception handlers to e200/e500 cores adding CONFIG_SPE_POSSIBLE
> and consequently guard __stup_ivors and __setup_cpu functions.
>
> Signed-off-by: Mihai Caraman <mihai.caraman@freescale•com>
> Cc: Scott Wood <scottwood@freescale•com>
> Cc: Alexander Graf <agraf@suse•de>
> ---
> v2:
> - use CONFIG_PPC_E500MC without CONFIG_E500
> - use elif defined()
>
> arch/powerpc/kernel/cpu_setup_fsl_booke.S | 12 +++++++++++-
> arch/powerpc/kernel/cputable.c | 5 +++++
> arch/powerpc/kernel/head_fsl_booke.S | 18 +++++++++++++-----
> arch/powerpc/platforms/Kconfig.cputype | 6 +++++-
> 4 files changed, 34 insertions(+), 7 deletions(-)
Acked-by: Scott Wood <scottwood@freescale•com>
-Scott
next prev parent reply other threads:[~2014-08-21 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 13:09 [PATCH v2 1/2] powerpc/booke: Restrict SPE exception handlers to e200/e500 cores Mihai Caraman
2014-08-20 13:09 ` [PATCH v2 2/2] powerpc/booke: Revert SPE/AltiVec common defines for interrupt numbers Mihai Caraman
2014-08-21 1:58 ` Scott Wood
2014-08-21 1:57 ` Scott Wood [this message]
2014-08-27 11:19 ` [PATCH v2 1/2] powerpc/booke: Restrict SPE exception handlers to e200/e500 cores Alexander Graf
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=1408586243.4058.96.camel@snotra.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=agraf@suse$(echo .)de \
--cc=kvm-ppc@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mihai.caraman@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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