summaryrefslogtreecommitdiffstats
path: root/crypto/Makefile
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2024-01-11 09:00:34 +0100
committerPaolo Bonzini <pbonzini@redhat.com>2024-02-08 14:41:06 +0100
commit8886640dade4ae2595fcdce511c8bcc716aa47d3 (patch)
treeffcf2f3b0e7c25fd1d9e8ddd3e37d462c9e4dc1c /crypto/Makefile
parentKVM: arm64: move ARM-specific defines to uapi/asm/kvm.h (diff)
downloadlinux-8886640dade4ae2595fcdce511c8bcc716aa47d3.tar.xz
linux-8886640dade4ae2595fcdce511c8bcc716aa47d3.zip
kvm: replace __KVM_HAVE_READONLY_MEM with Kconfig symbol
KVM uses __KVM_HAVE_* symbols in the architecture-dependent uapi/asm/kvm.h to mask unused definitions in include/uapi/linux/kvm.h. __KVM_HAVE_READONLY_MEM however was nothing but a misguided attempt to define KVM_CAP_READONLY_MEM only on architectures where KVM_CHECK_EXTENSION(KVM_CAP_READONLY_MEM) could possibly return nonzero. This however does not make sense, and it prevented userspace from supporting this architecture-independent feature without recompilation. Therefore, these days __KVM_HAVE_READONLY_MEM does not mask anything and is only used in virt/kvm/kvm_main.c. Userspace does not need to test it and there should be no need for it to exist. Remove it and replace it with a Kconfig symbol within Linux source code. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'crypto/Makefile')
0 files changed, 0 insertions, 0 deletions