From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Laurentiu Tudor <Laurentiu.Tudor@freescale.com>
Subject: Re: [PATCH] powerpc/e5500: Set r5 to point to cpu spec in setup_cpu_e5500()
Date: Fri, 16 Sep 2011 13:36:49 -0500 [thread overview]
Message-ID: <4E739741.3050202@freescale.com> (raw)
In-Reply-To: <1316187462-21074-1-git-send-email-galak@kernel.crashing.org>
On 09/16/2011 10:37 AM, Kumar Gala wrote:
> From: Laurentiu Tudor <Laurentiu.Tudor@freescale.com>
>
> e500mc and e5500 share some eary setup code that need r5 to point to the
> cpu spec structure. setup_cpu_e500mc() sets it but setup_cpu_e5500()
> didn't.
>
> This caused a crash on 32 bit e5500 running under hypervisor, when
> __setup_e500mc_ivors() tried to access the cpu features field.
>
> Signed-off-by: Laurentiu Tudor <Laurentiu.Tudor@freescale.com>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> arch/powerpc/kernel/cpu_setup_fsl_booke.S | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
Unless I missed something going in recently, there's nothing in the
mainline kernel that uses r5 in __setup_e500mc_ivors(). This is a fix
for code that is currently just in our SDK, and should be combined with
that code when it is posted. The interprocedural register allocation
could stand to be done more simply as well (why not just pick a
different register for lr, and leave r4 where it is?), and should be
documented.
-Scott
prev parent reply other threads:[~2011-09-16 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 15:37 [PATCH] powerpc/e5500: Set r5 to point to cpu spec in setup_cpu_e5500() Kumar Gala
2011-09-16 18:36 ` Scott Wood [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=4E739741.3050202@freescale.com \
--to=scottwood@freescale.com \
--cc=Laurentiu.Tudor@freescale.com \
--cc=galak@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 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.