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: Fri, 22 Jul 2011 18:23:05 +0530 [thread overview]
Message-ID: <4E2972B1.5070604@ti.com> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE896716203F2398D3A@dlee02.ent.ti.com>
On 7/22/2011 6:15 PM, Woodruff, Richard wrote:
>
>> From: linux-arm-kernel-bounces at lists.infradead.org [mailto:linux-arm-
>> kernel-bounces at lists.infradead.org] On Behalf Of Shilimkar, Santosh
>
>>> With fixed IRQ migration and forcing CPU0 into an infinite WFI loop,
>>> I can offline CPU0 and still have a running system.
>>>
>> The secure software runs only on CPU0 and that's the biggest limitation.
>> Other issues like hand-shake as you pointed out, power sequencing etc
>> can be worked around.
>
> As you know well some of the secure APIs work on CPU1 and others do not.
>
> I notice in other thread Russell made assumption about CPU1 being able to use all because it could run some. This is not the case.
>
I clarified that on the other thread.
Regards
Santosh
next prev parent reply other threads:[~2011-07-22 12:53 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
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 [this message]
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=4E2972B1.5070604@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).