diff options
| author | Christoffer Dall <christoffer.dall@linaro.org> | 2014-08-26 16:00:37 +0400 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2014-08-29 15:47:04 +0400 |
| commit | 0f8a4de3e088797576ac76200b634b802e5c7781 (patch) | |
| tree | fdadf9b707953e463d3d91c45109fc83179eef39 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | dc77d344b41f3ffdd3b02317597e717b0b799f46 (diff) | |
| download | linux-0f8a4de3e088797576ac76200b634b802e5c7781.tar.xz | |
KVM: Unconditionally export KVM_CAP_READONLY_MEM
The idea between capabilities and the KVM_CHECK_EXTENSION ioctl is that
userspace can, at run-time, determine if a feature is supported or not.
This allows KVM to being supporting a new feature with a new kernel
version without any need to update user space. Unfortunately, since the
definition of KVM_CAP_READONLY_MEM was guarded by #ifdef
__KVM_HAVE_READONLY_MEM, such discovery still required a user space
update.
Therefore, unconditionally export KVM_CAP_READONLY_MEM and change the
in-kernel conditional to rely on __KVM_HAVE_READONLY_MEM.
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions