diff options
author | 2025-01-06 18:16:26 +0530 | |
---|---|---|
committer | 2025-01-07 21:26:06 +0100 | |
commit | 0f0502b8865c0a4c402e73aeb0fb406acc19d0d2 (patch) | |
tree | ac2403a7ae384732a6c2604301c4f0952462f13b /scripts/generate_rust_analyzer.py | |
parent | x86/sev: Add Secure TSC support for SNP guests (diff) | |
download | wireguard-linux-0f0502b8865c0a4c402e73aeb0fb406acc19d0d2.tar.xz wireguard-linux-0f0502b8865c0a4c402e73aeb0fb406acc19d0d2.zip |
x86/sev: Change TSC MSR behavior for Secure TSC enabled guests
Secure TSC enabled guests should not write to the MSR_IA32_TSC (0x10) register
as the subsequent TSC value reads are undefined. On AMD, MSR_IA32_TSC is
intercepted by the hypervisor by default. MSR_IA32_TSC read/write accesses
should not exit to the hypervisor for such guests.
Accesses to MSR_IA32_TSC need special handling in the #VC handler for the
guests with Secure TSC enabled. Writes to MSR_IA32_TSC should be ignored and
flagged once with a warning, and reads of MSR_IA32_TSC should return the
result of the RDTSC instruction.
[ bp: Massage commit message. ]
Suggested-by: Borislav Petkov (AMD) <bp@alien8.de>
Signed-off-by: Nikunj A Dadhania <nikunj@amd.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
Link: https://lore.kernel.org/r/20250106124633.1418972-7-nikunj@amd.com
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions