From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: Possible regression in kexec on ARM ARMv6 and ARMv7 cores
Date: Thu, 20 Oct 2011 17:08:24 +0900 [thread overview]
Message-ID: <20111020080823.GA2716@verge.net.au> (raw)
In-Reply-To: <20111020070105.GA28548@mudshark.cambridge.arm.com>
On Thu, Oct 20, 2011 at 08:01:06AM +0100, Will Deacon wrote:
> On Thu, Oct 20, 2011 at 05:24:45AM +0100, Simon Horman wrote:
> > Hi Will, Hi All,
>
> Hi Simon,
Hi Will,
> > it appears that "ARM: proc: add definition of cpu_reset for
> > ARMv6 and ARMv7 cores" (f4daf06fc23b99df5ca5b3e892428b91e148cc52),
> > which was introduced for 3.1-rc1, causes a regression and that
> > kexec no longer works on ARM. The board that I am testing
> > on is a Renesas Mackerel which has an SH7372 (ARMv7) processor.
>
> Wow, I'm surprised the old code worked at all on an ARMv7 CPU! It's certainly
> highly unlikely to work by the letter of the architecture, so I guess the
> planets aligned in just the right way for your particular implementation.
>
> Please can you try my kexec/mmu-off patches? They should add the bits and
> pieces you need for kexec to work reliably on a UP system. I plan to finish
> these off next week in Prague so hopefully they'll hit mainline in the near
> future.
>
> https://github.com/wdeacon/linux-wd/commits/kexec/mmu-off
Thanks, I will try your patches and let you know how I go.
You mention UP in particular, which I will test.
Do you have any thoughts on SMP?
next prev parent reply other threads:[~2011-10-20 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 4:24 Possible regression in kexec on ARM ARMv6 and ARMv7 cores Simon Horman
2011-10-20 7:01 ` Will Deacon
2011-10-20 8:08 ` Simon Horman [this message]
2011-10-21 8:34 ` Simon Horman
2011-10-21 8:46 ` Will Deacon
2011-10-21 8:59 ` Simon Horman
2011-10-21 9:15 ` Will Deacon
2011-10-22 2:20 ` Simon Horman
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=20111020080823.GA2716@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).