summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/libxed.py
diff options
context:
space:
mode:
authorMichael Kelley <mhklinux@outlook.com>2025-03-19 00:49:19 +0300
committerWei Liu <wei.liu@kernel.org>2025-03-21 21:24:22 +0300
commit999ad14259a0d45cb3b616e2e95a7c8b622a7ecd (patch)
tree177df3483f8dd8f22d1a84354a5e08bc84b17d90 /tools/perf/scripts/python/libxed.py
parent621191d709b14882270dfd8ea5d7d6cdfebe2c35 (diff)
downloadlinux-999ad14259a0d45cb3b616e2e95a7c8b622a7ecd.tar.xz
x86/hyperv: Add comments about hv_vpset and var size hypercall input args
Current code varies in how the size of the variable size input header for hypercalls is calculated when the input contains struct hv_vpset. Surprisingly, this variation is correct, as different hypercalls make different choices for what portion of struct hv_vpset is treated as part of the variable size input header. The Hyper-V TLFS is silent on these details, but the behavior has been confirmed with Hyper-V developers. To avoid future confusion about these differences, add comments to struct hv_vpset, and to hypercall call sites with input that contains a struct hv_vpset. The comments describe the overall situation and the calculation that should be used at each particular call site. No functional change as only comments are updated. Signed-off-by: Michael Kelley <mhklinux@outlook.com> Link: https://lore.kernel.org/r/20250318214919.958953-1-mhklinux@outlook.com Signed-off-by: Wei Liu <wei.liu@kernel.org> Message-ID: <20250318214919.958953-1-mhklinux@outlook.com>
Diffstat (limited to 'tools/perf/scripts/python/libxed.py')
0 files changed, 0 insertions, 0 deletions