diff options
| author | Jason Andryuk <jason.andryuk@amd.com> | 2026-11-03 20:30:25 -0500 |
|---|---|---|
| committer | Borislav Petkov (AMD) <bp@alien8.de> | 2026-11-08 23:25:40 -0800 |
| commit | ea51d1a4c31fc8320c34f897dc5296a0bfc5c7ca (patch) | |
| tree | b031dd4b9150ad6c206d3814b43d4d90eefd7188 /scripts/const_structs.checkpatch | |
| parent | 7475ea8b58616b33c04afb976cf0fbaad9dd63fb (diff) | |
x86/CPU/AMD: Don't print reset reason in VMs
print_s5_reset_status_mmio() expects to read FCH MMIO on baremetal. VMs don't
have emulated FCH registers, so there is nothing to check. Add an early exit
when running on a hypervisor.
The real motivation is Xen PV domUs can't boot on Zen CPUs. PV domUs PTEs
contain system physical addresses - they don't have the concept of guest
physical addresses. domUs can only map physical addresses they are assigned, so
a domU fails to map the FCH MMIO addresses.
However set_pte() does not return failure, so ioremap() returns a pointer while
the PTEs are unpopulated. print_s5_reset_status_mmio() faults when reading
through the pointer, breaking the boot.
Limit the reset reason printing to baremetal only where it actually makes sense.
[ bp: Massage commit message. ]
Fixes: ab8131028710 ("x86/CPU/AMD: Print the reason for the last reset")
Suggested-by: Borislav Petkov <bp@alien8.de>
Signed-off-by: Jason Andryuk <jason.andryuk@amd.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
Reviewed-by: Yazen Ghannam <yazen.ghannam@amd.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20261104013026.185392-1-jason.andryuk@amd.com
Diffstat (limited to 'scripts/const_structs.checkpatch')
0 files changed, 0 insertions, 0 deletions
