diff options
| author | Amos Kong <akong@redhat.com> | 2012-03-09 12:17:40 +0800 |
|---|---|---|
| committer | Avi Kivity <avi@redhat.com> | 2012-04-08 12:47:00 +0300 |
| commit | 786a9f888bfbe70a36d0592b26037ca1e8c8da7f (patch) | |
| tree | cdaf0b4608c474decee66943d6ee39e6c411e58a /Makefile | |
| parent | a13007160f1b9ec7c67e28ec9254f197c5c08d7d (diff) | |
| download | linux-3.10-786a9f888bfbe70a36d0592b26037ca1e8c8da7f.tar.gz linux-3.10-786a9f888bfbe70a36d0592b26037ca1e8c8da7f.tar.bz2 linux-3.10-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 'Makefile')
0 files changed, 0 insertions, 0 deletions