summaryrefslogtreecommitdiff
path: root/tools/lib/python/kdoc/python_version.py
diff options
context:
space:
mode:
authorMichael Kelley <mhkelley58@gmail.com>2026-09-01 20:01:27 -0700
committerWei Liu <wei.liu@kernel.org>2026-09-13 22:35:49 +0000
commit7b74c117e2aac78e0f723e1c9c3644451c56b0d9 (patch)
tree22df4a09144c424169f4a2f0cfd832472488a99b /tools/lib/python/kdoc/python_version.py
parent0cdd57a4c56115af5d736b5b2d9310ad91494abc (diff)
downloadlinux-next-7b74c117e2aac78e0f723e1c9c3644451c56b0d9.tar.gz
linux-next-7b74c117e2aac78e0f723e1c9c3644451c56b0d9.zip
x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index()
hv_apicid_to_vp_index() currently uses the per-cpu hypercall input and output pages. This function is called when running in VTL2 and when running in an SEV-SNP CoCo VM with no paravisor. In the former case, the output page is allocated, but in the latter case it is not, so the hypervisor stores the output VP index in memory that has not been allocated by the guest. Fix this by using the input page for both input and output. The hypercall has very small input and output, so sharing the same page for both is straightforward. An alternative fix is to allocate the per-cpu output page when running in an SEV-SNP CoCo guest, but this uses significantly more memory, particularly with larger vCPUs counts. Fixes: 86c48271e0d6 ("x86/hyperv: Fix APIC ID and VP index confusion in hv_snp_boot_ap()") Signed-off-by: Michael Kelley <mhklinux@outlook.com> Reviewed-by: Tianyu Lan <tiala@microsoft.com> Signed-off-by: Wei Liu <wei.liu@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions