aboutsummaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorSingh, Brijesh <brijesh.singh@amd.com>2019-02-04 22:23:40 +0000
committerPaolo Bonzini <pbonzini@redhat.com>2019-03-18 09:39:57 +0100
commitcedc0ad539afbbb669dba9e73dfad2915bc1c25b (patch)
tree6a30f4e826caef075426512e0d6df704694ae8b8 /crypto
parent2ddb89b00f947f785c9ca6742f28f954e3b75e62 (diff)
downloadqemu-cedc0ad539afbbb669dba9e73dfad2915bc1c25b.zip
qemu-cedc0ad539afbbb669dba9e73dfad2915bc1c25b.tar.gz
qemu-cedc0ad539afbbb669dba9e73dfad2915bc1c25b.tar.bz2
target/i386: sev: Do not pin the ram device memory region
The RAM device presents a memory region that should be handled as an IO region and should not be pinned. In the case of the vfio-pci, RAM device represents a MMIO BAR and the memory region is not backed by pages hence KVM_MEMORY_ENCRYPT_REG_REGION fails to lock the memory range. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1667249 Cc: Alex Williamson <alex.williamson@redhat.com> Cc: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Brijesh Singh <brijesh.singh@amd.com> Message-Id: <20190204222322.26766-3-brijesh.singh@amd.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions