summaryrefslogtreecommitdiff
path: root/tools/verification
diff options
context:
space:
mode:
authorDexuan Cui <decui@microsoft.com>2023-08-24 11:07:09 +0300
committerWei Liu <wei.liu@kernel.org>2023-08-25 03:04:57 +0300
commit23378295042a4bcaeec350733a4771678e7a1f3a (patch)
tree96e4447fe9da4a905966d611f98ace45fb4ea714 /tools/verification
parentd3a9d7e49d15316f68f4347f48adcd1665834980 (diff)
downloadlinux-23378295042a4bcaeec350733a4771678e7a1f3a.tar.xz
Drivers: hv: vmbus: Bring the post_msg_page back for TDX VMs with the paravisor
The post_msg_page was removed in commit 9a6b1a170ca8 ("Drivers: hv: vmbus: Remove the per-CPU post_msg_page") However, it turns out that we need to bring it back, but only for a TDX VM with the paravisor: in such a VM, the hyperv_pcpu_input_arg is not decrypted, but the HVCALL_POST_MESSAGE in such a VM needs a decrypted page as the hypercall input page: see the comments in hyperv_init() for a detailed explanation. Except for HVCALL_POST_MESSAGE and HVCALL_SIGNAL_EVENT, the other hypercalls in a TDX VM with the paravisor still use hv_hypercall_pg and must use the hyperv_pcpu_input_arg (which is encrypted in such a VM), when a hypercall input page is used. Signed-off-by: Dexuan Cui <decui@microsoft.com> Reviewed-by: Tianyu Lan <tiala@microsoft.com> Reviewed-by: Michael Kelley <mikelley@microsoft.com> Signed-off-by: Wei Liu <wei.liu@kernel.org> Link: https://lore.kernel.org/r/20230824080712.30327-8-decui@microsoft.com
Diffstat (limited to 'tools/verification')
0 files changed, 0 insertions, 0 deletions