From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: do not mark CPU 0 as hotpluggable
Date: Thu, 21 Jul 2011 11:03:04 +0530 [thread overview]
Message-ID: <4E27BA10.3060203@ti.com> (raw)
In-Reply-To: <4E2796DA.80001@gmail.com>
On 7/21/2011 8:32 AM, Rob Herring wrote:
> On 07/20/2011 06:32 PM, Mike Turquette wrote:
>> A quick poll of the ARM platforms that implement CPU Hotplug support
>> shows that every platform treats CPU 0 as a special case that cannot be
>> hotplugged. In fact every platform has identical code for
>> platform_cpu_die which returns -EPERM in the case of CPU 0.
>>
>> The user-facing sysfs interfaces should reflect this by not populating
>> an 'online' entry for CPU 0 at all. This better reflects reality by
>> making it clear to users that CPU 0 cannot be hotplugged.
>>
>> This patch prevents CPU 0 from being marked as hotpluggable on all ARM
>> platforms during CPU registration. This in turn prevents the creation
>> of an 'online' sysfs interface for that CPU.
>>
> Unless there is a kernel limitation why CPU0 can't be hot unplugged,
> then this should remain a platform decision. This may be another case of
> everybody just copying other platforms' code, not a platform limitation.
>
Just talking on behalf of OMAP, we can't offline CPU0 and limitation
would remain in future OMAPs too.
Regards
Santosh
next prev parent reply other threads:[~2011-07-21 5:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 23:32 [PATCH] ARM: do not mark CPU 0 as hotpluggable Mike Turquette
2011-07-21 3:02 ` Rob Herring
2011-07-21 5:33 ` Santosh Shilimkar [this message]
2011-07-21 13:30 ` Russell King - ARM Linux
2011-07-22 4:56 ` Santosh Shilimkar
2011-07-22 12:45 ` Woodruff, Richard
2011-07-22 12:53 ` Santosh Shilimkar
2011-08-12 1:31 ` Turquette, Mike
2011-07-21 7:45 ` Russell King - ARM Linux
2011-07-21 21:22 ` Woodruff, Richard
2011-07-21 22:18 ` Turquette, Mike
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=4E27BA10.3060203@ti.com \
--to=santosh.shilimkar@ti.com \
--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).