diff options
author | Sudeep Holla <sudeep.holla@arm.com> | 2019-06-12 13:51:37 +0100 |
---|---|---|
committer | Will Deacon <will@kernel.org> | 2019-08-15 11:12:03 +0100 |
commit | d55c5f28afafb6b1f0a6978916b23338b383faab (patch) | |
tree | f9f03d19dc8328624ac57d92da43c8155561b8d5 /scripts | |
parent | 9ffeb6d08c3a4bbd7b1e33711b241f511e2ded79 (diff) | |
download | linux-d55c5f28afafb6b1f0a6978916b23338b383faab.tar.bz2 |
arm64: smp: disable hotplug on trusted OS resident CPU
The trusted OS may reject CPU_OFF calls to its resident CPU, so we must
avoid issuing those. We never migrate a Trusted OS and we already take
care to prevent CPU_OFF PSCI call. However, this is not reflected
explicitly to the userspace. Any user can attempt to hotplug trusted OS
resident CPU. The entire motion of going through the various state
transitions in the CPU hotplug state machine gets executed and the
PSCI layer finally refuses to make CPU_OFF call.
This results is unnecessary unwinding of CPU hotplug state machine in
the kernel. Instead we can mark the trusted OS resident CPU as not
available for hotplug, so that the user attempt or request to do the
same will get immediately rejected.
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions