From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MBPkD-0000b3-Gz for qemu-devel@nongnu.org; Tue, 02 Jun 2009 04:53:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MBPk8-0000Y6-UQ for qemu-devel@nongnu.org; Tue, 02 Jun 2009 04:53:17 -0400 Received: from [199.232.76.173] (port=32768 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MBPk8-0000Xu-EE for qemu-devel@nongnu.org; Tue, 02 Jun 2009 04:53:12 -0400 Received: from mx2.redhat.com ([66.187.237.31]:60073) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MBPk7-0001HU-U8 for qemu-devel@nongnu.org; Tue, 02 Jun 2009 04:53:12 -0400 Message-ID: <4A24E7F7.9040604@redhat.com> Date: Tue, 02 Jun 2009 11:51:03 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 7/7] [RFC] pci bus: preliminary for multi pci bus support. References: <1243924970-17545-1-git-send-email-yamahata@valinux.co.jp> <1243924970-17545-8-git-send-email-yamahata@valinux.co.jp> <4A24D10F.1020603@redhat.com> <20090602074600.GG9176%yamahata@valinux.co.jp> In-Reply-To: <20090602074600.GG9176%yamahata@valinux.co.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Isaku Yamahata Cc: armbru@redhat.com, paul@codesourcery.com, mtosatti@redhat.com, qemu-devel@nongnu.org, mst@redhat.com Isaku Yamahata wrote: > On Tue, Jun 02, 2009 at 10:13:19AM +0300, Avi Kivity wrote: > >> Isaku Yamahata wrote: >> >>> This patch is preliminary for multi pci bus support to >>> add -pci option. >>> >>> >> What is the motivation for this work? >> > > -pci might be too generic. -pci_bridge or something else might be > better. I think, eventually they would be replaced with config file work. > So this option isn't so important. > > The short term motivation is 128+ pci slot support. > I know Markus has tried on kvm before and was rejected because > of scalability. As he also wants it, I'm willing to collaborate with him. > Thanks for the explanation. > The long term motivation is to support MMCFG and PCIe port emulator, > then eventually PCIe native direct attach support including > PCIe native functionality like AER. > This requires more newer chipset emulation than piix and more. > Yes, this is definitely interesting. -- error compiling committee.c: too many arguments to function