summaryrefslogtreecommitdiff
path: root/drivers/cpufreq/cppc_cpufreq.c
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2023-01-12 14:33:19 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2023-01-18 19:58:15 +0100
commit182da6f2b81a78709c58021542fb694f8ed80774 (patch)
tree106ec46adb9f51260aee651551680661c45227bb /drivers/cpufreq/cppc_cpufreq.c
parent5dc4c995db9eb45f6373a956eb1f69460e69e6d4 (diff)
downloadlinux-182da6f2b81a78709c58021542fb694f8ed80774.tar.gz
linux-182da6f2b81a78709c58021542fb694f8ed80774.tar.bz2
linux-182da6f2b81a78709c58021542fb694f8ed80774.zip
ACPI: PRM: Check whether EFI runtime is available
The ACPI PRM address space handler calls efi_call_virt_pointer() to execute PRM firmware code, but doing so is only permitted when the EFI runtime environment is available. Otherwise, such calls are guaranteed to result in a crash, and must therefore be avoided. Given that the EFI runtime services may become unavailable after a crash occurring in the firmware, we need to check this each time the PRM address space handler is invoked. If the EFI runtime services were not available at registration time to being with, don't install the address space handler at all. Fixes: cefc7ca46235 ("ACPI: PRM: implement OperationRegion handler for the PlatformRtMechanism subtype") Signed-off-by: Ard Biesheuvel <ardb@kernel.org> Cc: All applicable <stable@vger.kernel.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/cppc_cpufreq.c')
0 files changed, 0 insertions, 0 deletions