From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGddp-0004Cb-HD for qemu-devel@nongnu.org; Tue, 16 Jun 2009 14:44:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGddl-0004Ak-Qx for qemu-devel@nongnu.org; Tue, 16 Jun 2009 14:44:17 -0400 Received: from [199.232.76.173] (port=60625 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGddl-0004Ab-Jk for qemu-devel@nongnu.org; Tue, 16 Jun 2009 14:44:13 -0400 Received: from mail2.shareable.org ([80.68.89.115]:36220) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MGddl-00036o-3Y for qemu-devel@nongnu.org; Tue, 16 Jun 2009 14:44:13 -0400 Date: Tue, 16 Jun 2009 19:44:04 +0100 From: Jamie Lokier Subject: Re: Configuration vs. compat hints [was Re: [Qemu-devel] [PATCHv3 03/13] qemu: add routines to manage PCI capabilities] Message-ID: <20090616184404.GJ11893@shareable.org> References: <4A364FE0.40204@redhat.com> <4A3651EB.3070204@codemonkey.ws> <4A36555A.4090303@redhat.com> <4A3659A0.3050108@codemonkey.ws> <4A366348.1030202@redhat.com> <1245083229.3222.103.camel@blaa> <4A368F12.2090504@codemonkey.ws> <1245154451.11407.22.camel@blaa> <4A378FE5.5050303@redhat.com> <1245155992.30082.8.camel@blaa> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1245155992.30082.8.camel@blaa> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark McLoughlin Cc: Carsten Otte , Rusty Russell , kvm@vger.kernel.org, "Michael S. Tsirkin" , Glauber Costa , dlaor@redhat.com, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Avi Kivity , Paul Brook Mark McLoughlin wrote: > > Worst case we hardcode those numbers (gasp, faint). > > Maybe we can just add the open slots to the -help output. That'd be nice > and clean. Make them part of the machine configuration. After all, they are part of the machine configuration, and ACPI, BIOS etc. need to know about all the machine slots anyway. Having said that, I prefer the idea that slot allocation is handled either in Qemu, or in a separate utility called qemu-machine-config (for working with machine configs), or in a library libqemu-machine-config.so. I particularly don't like the idea of arcane machine-dependent slot allocation knowledge living in libvirt, because it needs to be in Qemu anyway for non-libvirt users. No point in having two implementations of something tricky and likely to have machine quirks, if one will do. -- Jamie