diff options
| author | Amos Kong | 2012-03-09 05:17:40 +0100 |
|---|---|---|
| committer | Avi Kivity | 2012-04-08 11:47:00 +0200 |
| commit | 786a9f888bfbe70a36d0592b26037ca1e8c8da7f (patch) | |
| tree | cdaf0b4608c474decee66943d6ee39e6c411e58a /include/linux/kvm_host.h | |
| parent | KVM: resize kvm_io_range array dynamically (diff) | |
| download | kernel-qcow2-linux-786a9f888bfbe70a36d0592b26037ca1e8c8da7f.tar.gz kernel-qcow2-linux-786a9f888bfbe70a36d0592b26037ca1e8c8da7f.tar.xz kernel-qcow2-linux-786a9f888bfbe70a36d0592b26037ca1e8c8da7f.zip | |
KVM: set upper bounds for iobus dev to limit userspace
kvm_io_bus devices are used for ioevent, pit, pic, ioapic,
coalesced_mmio.
Currently Qemu only emulates one PCI bus, it contains 32 slots,
one slot contains 8 functions, maximum of supported PCI devices:
1 * 32 * 8 = 256. One virtio-blk takes one iobus device,
one virtio-net(vhost=on) takes two iobus devices.
The maximum of coalesced mmio zone is 100, each zone
has an iobus devices. So 300 io_bus devices are not enough.
Set an upper bounds for kvm_io_range to limit userspace.
1000 is a very large limit and not bloat the typical user.
Signed-off-by: Amos Kong <akong@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'include/linux/kvm_host.h')
| -rw-r--r-- | include/linux/kvm_host.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h index ba9fb4a9762d..3a2cea616283 100644 --- a/include/linux/kvm_host.h +++ b/include/linux/kvm_host.h @@ -68,7 +68,7 @@ struct kvm_io_range { struct kvm_io_device *dev; }; -#define NR_IOBUS_DEVS 300 +#define NR_IOBUS_DEVS 1000 struct kvm_io_bus { int dev_count; |