From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
marc.zyngier@arm.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org,
Andre Przywara <andre.przywara@arm.com>,
Vadim.Lomovtsev@caviumnetworks.com
Subject: Re: [PATCH v4 4/5] arm64: Verify CPU errata work arounds on hotplugged CPU
Date: Fri, 22 Apr 2016 14:43:57 +0100 [thread overview]
Message-ID: <571A2A9D.7070702@arm.com> (raw)
In-Reply-To: <20160422134053.GL2998@e104818-lin.cambridge.arm.com>
On 22/04/16 14:40, Catalin Marinas wrote:
> On Fri, Apr 22, 2016 at 12:25:34PM +0100, Suzuki K. Poulose wrote:
>> CPU Errata work arounds are detected and applied to the
>> kernel code at boot time and the data is then freed up.
>> If a new hotplugged CPU requires a work around which
>> was not applied at boot time, there is nothing we can
>> do but simply fail the booting.
>>
>> Cc: Will Deacon <will.deacon@arm.com>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Cc: Andre Przywara <andre.przywara@arm.com>
>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>
> I think Will commented on this previously. Was a decision made to leave
> this patch as it is and subsequently add support for enabling local
> workarounds for hot-plugged CPUs? I'm fine with this given that most
Yes. Applying work arounds for a hot-plugged CPU will be addressed in a
new series. I updated the cover letter, but missed to update the same here.
>
> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Thanks
Suzuki
next prev parent reply other threads:[~2016-04-22 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 11:25 [PATCH v4 0/5] arm64: Fix behavior of maxcpus=n Suzuki K Poulose
2016-04-22 11:25 ` [PATCH v4 1/5] arm64: cpufeature: Add scope for capability check Suzuki K Poulose
2016-04-22 13:29 ` Catalin Marinas
2016-04-22 11:25 ` [PATCH v4 2/5] arm64: Allow a capability to be checked on a single CPU Suzuki K Poulose
2016-04-22 13:32 ` Catalin Marinas
2016-04-22 11:25 ` [PATCH v4 3/5] irqchip/gic: Restore CPU interface checking Suzuki K Poulose
2016-04-22 13:33 ` Catalin Marinas
2016-04-22 11:25 ` [PATCH v4 4/5] arm64: Verify CPU errata work arounds on hotplugged CPU Suzuki K Poulose
2016-04-22 13:40 ` Catalin Marinas
2016-04-22 13:43 ` Suzuki K Poulose [this message]
2016-04-22 11:25 ` [PATCH v4 5/5] arm64: Fix behavior of maxcpus=N Suzuki K Poulose
2016-04-22 13:50 ` 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=571A2A9D.7070702@arm.com \
--to=suzuki.poulose@arm.com \
--cc=Vadim.Lomovtsev@caviumnetworks.com \
--cc=andre.przywara@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