From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH v3] KVM: Resize kvm_io_range array dynamically Date: Wed, 29 Feb 2012 15:19:45 +0100 Message-ID: <4F4E3401.4010703@siemens.com> References: <20120229052422.9775.34485.stgit@dhcp-8-167.nay.redhat.com> <20120229133034.13884.76262.stgit@dhcp-8-167.nay.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, jasowang@redhat.com, mtosatti@redhat.com, alex.williamson@redhat.com, avi@redhat.com, levinsasha928@gmail.com To: Amos Kong Return-path: Received: from david.siemens.de ([192.35.17.14]:19320 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030926Ab2B2OTw (ORCPT ); Wed, 29 Feb 2012 09:19:52 -0500 In-Reply-To: <20120229133034.13884.76262.stgit@dhcp-8-167.nay.redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2012-02-29 14:30, Amos Kong wrote: > 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. The maximum of coalesced mmio zone is 100, > each zone has an iobus devices. 300 io_bus devices is not enough. > > This patch makes the kvm_io_range array can be resized dynamically. Is there any limit, or can userspace allocate arbitrary amounts of kernel memory this way? Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux