From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Fixing CPU Hotplug for RealView Platforms
Date: Wed, 8 Dec 2010 20:20:43 +0000 [thread overview]
Message-ID: <20101208202043.GR9777@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <007501cb9636$c0a54c90$41efe5b0$@deacon@arm.com>
On Tue, Dec 07, 2010 at 05:47:00PM -0000, Will Deacon wrote:
> Hi Russell,
> > What if we fixed the cpu_reset functions for v6 and v7, and when a CPU
> > is taken offline, we actually go through a proper shutdown of that CPU
> > and call the reset vector, re-entering the boot loader?
>
> This will certainly solve our problem, but people might complain that it's
> too heavyweight :)
Our current hot plug-in code already re-runs most of the secondary CPU
initialization in the kernel - we reset the stack and jump back to
secondary_start_kernel().
What we'll be adding to that is the overheads in the boot loader (which
would happen at the point we go offline) and getting back to the kernel
code. From that point, the additional things are looking up the CPU
type, calling its setup function, and enabling the MMU.
Everything from that point on would be identical to what already happens
on the hot plug-in path.
next prev parent reply other threads:[~2010-12-08 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 16:43 [RFC] Fixing CPU Hotplug for RealView Platforms Will Deacon
2010-12-07 17:18 ` Russell King - ARM Linux
2010-12-07 17:47 ` Will Deacon
2010-12-08 6:03 ` Santosh Shilimkar
2010-12-08 13:20 ` Will Deacon
2010-12-08 20:20 ` Russell King - ARM Linux [this message]
2010-12-18 17:10 ` Russell King - ARM Linux
2010-12-18 17:44 ` Will Deacon
2010-12-18 19:22 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2010-12-20 8:16 Vincent Guittot
2011-01-03 10:46 ` Russell King - ARM Linux
2011-01-03 17:39 ` Vincent Guittot
2011-01-03 18:03 ` Russell King - ARM Linux
2011-01-04 8:55 ` Vincent Guittot
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=20101208202043.GR9777@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).