linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, marc.zyngier@arm.com,
	linux-kernel@vger.kernel.org, will.deacon@arm.com,
	catalin.marinas@arm.com
Subject: Re: [PATCH v2 2/6] arm64: Move kill_cpu_early to smp.c
Date: Tue, 1 Dec 2015 18:10:17 +0000	[thread overview]
Message-ID: <565DE289.2000105@arm.com> (raw)
In-Reply-To: <20151201175254.GD29045@leverpostej>

On 01/12/15 17:52, Mark Rutland wrote:
> On Tue, Dec 01, 2015 at 05:38:54PM +0000, Suzuki K. Poulose wrote:
>> On 01/12/15 16:31, Mark Rutland wrote:
>
> [...]
>
>>> We need stuck-in-the-kernel flag to account for CPUs which didn't manage
>>> to turn the MMU on (which are either in the spin-table, or failed when
>>> they were individually onlined).
>>
>> Did you mean to say "turn the MMU off" ?
>
> No, I mean CPUs which were unable to turn the MMU on in the first place.
> Perhaps they entered the spin-table but were never individually onlined,
> perhaps they didn't support the kernel page size, etc.
>
> When CPUs exit the kernel via PSCI they never switch the MMU off within
> the kernel.

OK. So the flag will also be used for CPUs which are stuck-in-the-kernel
with MMU turned on. e.g, a CPU (using spin-table) we try to bring down
in kill_cpu_early(). Correct ?

Thanks
Suzuki


  reply	other threads:[~2015-12-01 18:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 15:12 [PATCH v2 0/6] arm64: cpufeature: Add sanity check for ASIDBits Suzuki K. Poulose
2015-12-01 15:12 ` [PATCH v2 1/6] arm64: Introduce kill_cpu_early Suzuki K. Poulose
2015-12-01 15:12 ` [PATCH v2 2/6] arm64: Move kill_cpu_early to smp.c Suzuki K. Poulose
2015-12-01 15:28   ` Mark Rutland
2015-12-01 16:07     ` Suzuki K. Poulose
2015-12-01 16:31       ` Mark Rutland
2015-12-01 17:38         ` Suzuki K. Poulose
2015-12-01 17:52           ` Mark Rutland
2015-12-01 18:10             ` Suzuki K. Poulose [this message]
2015-12-01 18:50               ` Mark Rutland
2015-12-03 16:36                 ` Suzuki K. Poulose
2015-12-03 17:08                   ` Mark Rutland
2015-12-01 15:12 ` [PATCH v2 3/6] arm64: Enable CPU capability verification for !CONFIG_HOTPLUG_CPU Suzuki K. Poulose
2015-12-01 15:12 ` [PATCH v2 4/6] arm64: Add hook for checking early CPU features Suzuki K. Poulose
2015-12-01 15:12 ` [PATCH v2 5/6] arm64: Add helper for extracting ASIDBits Suzuki K. Poulose
2015-12-01 15:12 ` [PATCH v2 6/6] arm64: Ensure the secondary CPUs have safe ASIDBits size Suzuki K. Poulose
2015-12-01 15:15 ` [PATCH v2 0/6] arm64: cpufeature: Add sanity check for ASIDBits Suzuki K. Poulose

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=565DE289.2000105@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.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 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).