summaryrefslogtreecommitdiff
path: root/Documentation/crypto
diff options
context:
space:
mode:
authorThomas Hellstrom <thellstrom@vmware.com>2019-11-14 16:03:18 +0300
committerThomas Hellstrom <thellstrom@vmware.com>2020-01-15 13:46:57 +0300
commitaf4eaf10978e5b14660020f39e619059489cc694 (patch)
tree0a8c5c211f8a5c66b90ec049349bdd33195226e3 /Documentation/crypto
parent71e7274066c646bb3d9da39d2f4db0a6404c0a2d (diff)
downloadlinux-af4eaf10978e5b14660020f39e619059489cc694.tar.xz
drm/vmwgfx: Don't use the HB port if memory encryption is active
With memory encryption active, the hypervisor typically can't read the guest memory using the HB port, since it is encrypted using a key known only to the guest. In that case fall back to processing 4 bytes at a time using the ordinary backdoor port. The other option would be to use unencrypted bounce buffers for the hypervisor to read out from or write into, but given the limited message sizes it appears more efficient to just fall back to the ordinary backdoor port. Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com> Reviewed-by: Roland Scheidegger <sroland@vmware.com>
Diffstat (limited to 'Documentation/crypto')
0 files changed, 0 insertions, 0 deletions