linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Suzuki.Poulose@arm.com (Suzuki K. Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64: CPU Hotplug: can't enable more cpus than maxcpus value (kernel 4.5)
Date: Thu, 3 Mar 2016 15:41:43 +0000	[thread overview]
Message-ID: <56D85B37.8020306@arm.com> (raw)
In-Reply-To: <20160303151200.GE19139@leverpostej>

On 03/03/16 15:12, Mark Rutland wrote:
> On Thu, Mar 03, 2016 at 02:59:29PM +0000, Suzuki K. Poulose wrote:
>> On 03/03/16 14:42, Mark Rutland wrote:
>> We don't have this limitation anymore, as we can check if the booting CPU
>> has any conflicting/missing features w.r.t the established set and fail the
>> booting if it does.
>
> While we do this, that's more of a last-ditch effort as opposed to a
> general solution, and I'm not sure it's complete.
>
> What happens when we online a CPU that we determine needs a new erratum
> workaround applied? I didn't think we prohibited onlining in that case.

Right, the erratas can't be applied, as we would have free'd them already.


Cheers
Suzuki

  reply	other threads:[~2016-03-03 15:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 14:17 ARM64: CPU Hotplug: can't enable more cpus than maxcpus value (kernel 4.5) Vadim Lomovtsev
2016-03-03 14:42 ` Mark Rutland
2016-03-03 14:59   ` Suzuki K. Poulose
2016-03-03 15:01     ` Suzuki K. Poulose
2016-03-03 15:12     ` Mark Rutland
2016-03-03 15:41       ` Suzuki K. Poulose [this message]
2016-03-07 17:22         ` Suzuki K. Poulose
2016-03-07 17:18       ` Catalin Marinas

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=56D85B37.8020306@arm.com \
    --to=suzuki.poulose@arm.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).