On 14/04/16 18:39, Will Deacon wrote:
On Wed, Apr 06, 2016 at 12:24:13PM +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.
Hmm, wouldn't it be better not to free the alternative text for errata
workarounds instead?
We could. I don't have a strong opinion. If there are no objections, I could
adopt it.