From: Simon Horman <horms@verge.net.au>
To: Will Deacon <will.deacon@arm.com>
Cc: Dave Martin <dave.martin@linaro.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Frank Hofmann <frank.hofmann@tomtom.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Possible regression in kexec on ARM ARMv6 and ARMv7 cores
Date: Fri, 21 Oct 2011 17:59:58 +0900 [thread overview]
Message-ID: <20111021085958.GC21850@verge.net.au> (raw)
In-Reply-To: <20111021084641.GA30168@mudshark.cambridge.arm.com>
On Fri, Oct 21, 2011 at 09:46:41AM +0100, Will Deacon wrote:
> On Fri, Oct 21, 2011 at 09:34:26AM +0100, Simon Horman wrote:
> > I have tested the kexec/mmu-off branch of your tree on the UP board
> > I mentioned above and kexec works :)
>
> Hurrah! Thanks for giving it a spin.
>
> > > You mention UP in particular, which I will test.
> > > Do you have any thoughts on SMP?
>
> Yes. Currently [i.e. on my branch above] you can do SMP kexec using the CPU
> hotplug platform_cpu_kill callback to take down the CPUs in some
> platform-specific manner.
Thanks, I will take a look into it.
> The more difficult case is when you want to offline the secondary CPUs into
> a pen and then boot them in the new kernel. I did get some of this working,
> but there are outstanding issues with whether the pen should be at a fixed
> location or not. If not, then we need a way to tell the new kernel where it
> is, which may involve updating the DT blob...
Is the implication that the (working) callback method does not
give the second kernel any secondary CPUs?
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Possible regression in kexec on ARM ARMv6 and ARMv7 cores
Date: Fri, 21 Oct 2011 08:59:58 +0000 [thread overview]
Message-ID: <20111021085958.GC21850@verge.net.au> (raw)
In-Reply-To: <20111021084641.GA30168@mudshark.cambridge.arm.com>
On Fri, Oct 21, 2011 at 09:46:41AM +0100, Will Deacon wrote:
> On Fri, Oct 21, 2011 at 09:34:26AM +0100, Simon Horman wrote:
> > I have tested the kexec/mmu-off branch of your tree on the UP board
> > I mentioned above and kexec works :)
>
> Hurrah! Thanks for giving it a spin.
>
> > > You mention UP in particular, which I will test.
> > > Do you have any thoughts on SMP?
>
> Yes. Currently [i.e. on my branch above] you can do SMP kexec using the CPU
> hotplug platform_cpu_kill callback to take down the CPUs in some
> platform-specific manner.
Thanks, I will take a look into it.
> The more difficult case is when you want to offline the secondary CPUs into
> a pen and then boot them in the new kernel. I did get some of this working,
> but there are outstanding issues with whether the pen should be at a fixed
> location or not. If not, then we need a way to tell the new kernel where it
> is, which may involve updating the DT blob...
Is the implication that the (working) callback method does not
give the second kernel any secondary CPUs?
WARNING: multiple messages have this Message-ID (diff)
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: Fri, 21 Oct 2011 17:59:58 +0900 [thread overview]
Message-ID: <20111021085958.GC21850@verge.net.au> (raw)
In-Reply-To: <20111021084641.GA30168@mudshark.cambridge.arm.com>
On Fri, Oct 21, 2011 at 09:46:41AM +0100, Will Deacon wrote:
> On Fri, Oct 21, 2011 at 09:34:26AM +0100, Simon Horman wrote:
> > I have tested the kexec/mmu-off branch of your tree on the UP board
> > I mentioned above and kexec works :)
>
> Hurrah! Thanks for giving it a spin.
>
> > > You mention UP in particular, which I will test.
> > > Do you have any thoughts on SMP?
>
> Yes. Currently [i.e. on my branch above] you can do SMP kexec using the CPU
> hotplug platform_cpu_kill callback to take down the CPUs in some
> platform-specific manner.
Thanks, I will take a look into it.
> The more difficult case is when you want to offline the secondary CPUs into
> a pen and then boot them in the new kernel. I did get some of this working,
> but there are outstanding issues with whether the pen should be at a fixed
> location or not. If not, then we need a way to tell the new kernel where it
> is, which may involve updating the DT blob...
Is the implication that the (working) callback method does not
give the second kernel any secondary CPUs?
next prev parent reply other threads:[~2011-10-21 8:59 UTC|newest]
Thread overview: 24+ 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 4:24 ` Simon Horman
2011-10-20 4:24 ` Simon Horman
2011-10-20 7:01 ` Will Deacon
2011-10-20 7:01 ` Will Deacon
2011-10-20 7:01 ` Will Deacon
2011-10-20 8:08 ` Simon Horman
2011-10-20 8:08 ` Simon Horman
2011-10-20 8:08 ` Simon Horman
2011-10-21 8:34 ` Simon Horman
2011-10-21 8:34 ` Simon Horman
2011-10-21 8:34 ` Simon Horman
2011-10-21 8:46 ` Will Deacon
2011-10-21 8:46 ` Will Deacon
2011-10-21 8:46 ` Will Deacon
2011-10-21 8:59 ` Simon Horman [this message]
2011-10-21 8:59 ` Simon Horman
2011-10-21 8:59 ` Simon Horman
2011-10-21 9:15 ` Will Deacon
2011-10-21 9:15 ` Will Deacon
2011-10-21 9:15 ` Will Deacon
2011-10-22 2:20 ` Simon Horman
2011-10-22 2:20 ` Simon Horman
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=20111021085958.GC21850@verge.net.au \
--to=horms@verge.net.au \
--cc=dave.martin@linaro.org \
--cc=frank.hofmann@tomtom.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=will.deacon@arm.com \
/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.