diff options
| author | Christian Borntraeger | 2008-07-25 15:50:04 +0200 |
|---|---|---|
| committer | Avi Kivity | 2008-07-27 10:35:47 +0200 |
| commit | 99e65c92f2bbf84f43766a8bf701e36817d62822 (patch) | |
| tree | c7ad277189ab20fbb1041fba994099abbd96bc41 /drivers/s390/sysinfo.c | |
| parent | KVM: s390: Advertise KVM_CAP_USER_MEMORY (diff) | |
| download | kernel-qcow2-linux-99e65c92f2bbf84f43766a8bf701e36817d62822.tar.gz kernel-qcow2-linux-99e65c92f2bbf84f43766a8bf701e36817d62822.tar.xz kernel-qcow2-linux-99e65c92f2bbf84f43766a8bf701e36817d62822.zip | |
KVM: s390: Fix guest kconfig
Cornelia Huck noticed that a modular virtio without kvm guest support
leads to a build error in the s390 virtio transport:
CONFIG_VIRTIO=m leads to
ERROR: "vmem_add_mapping" [drivers/s390/kvm/kvm_virtio.ko] undefined!
ERROR: "max_pfn" [drivers/s390/kvm/kvm_virtio.ko] undefined!
ERROR: "vmem_remove_mapping" [drivers/s390/kvm/kvm_virtio.ko] undefined!
The virtio transport only works with kvm guest support and only as a
builtin. Lets change the build process of drivers/s390/kvm/kvm_virtio.c
to depend on kvm guest support, which is also a bool.
CONFIG_S390_GUEST already selects CONFIG_VIRTIO, that should prevent
CONFIG_S390_GUEST=y CONFIG_VIRTIO=n situations.
CC: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Diffstat (limited to 'drivers/s390/sysinfo.c')
0 files changed, 0 insertions, 0 deletions