From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MGAq2-0003yk-Jy
	for qemu-devel@nongnu.org; Mon, 15 Jun 2009 07:58:58 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MGApx-0003r6-PH
	for qemu-devel@nongnu.org; Mon, 15 Jun 2009 07:58:58 -0400
Received: from [199.232.76.173] (port=33280 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MGApx-0003qp-Ls
	for qemu-devel@nongnu.org; Mon, 15 Jun 2009 07:58:53 -0400
Received: from mx2.redhat.com ([66.187.237.31]:48243)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1MGApw-00064U-Uo
	for qemu-devel@nongnu.org; Mon, 15 Jun 2009 07:58:53 -0400
Message-ID: <4A3636FA.1040609@redhat.com>
Date: Mon, 15 Jun 2009 14:56:42 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: Configuration vs. compat hints [was Re: [Qemu-devel] [PATCHv3
	03/13] qemu: add routines to manage PCI capabilities]
References: <1244796209.16425.20.camel@blaa> <4A326B5C.5010501@codemonkey.ws>
	<1244821292.30522.56.camel@blaa> <4A327E4A.7010300@codemonkey.ws>
	<1244825303.26769.19.camel@blaa> <20090614095016.GA7560@redhat.com>
	<1245056916.6891.31.camel@blaa> <4A3613EC.6030608@redhat.com>
	<20090615103249.GB6351@redhat.com> <4A363012.8050409@redhat.com>
	<20090615114858.GG6351@redhat.com>
In-Reply-To: <20090615114858.GG6351@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Mark McLoughlin <markmc@redhat.com>, kvm@vger.kernel.org, Carsten Otte <cotte@de.ibm.com>, Glauber Costa <glommer@redhat.com>, Rusty Russell <rusty@rustcorp.com.au>, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl <blauwirbel@gmail.com>, Christian Borntraeger <borntraeger@de.ibm.com>, Paul Brook <paul@codesourcery.com>

On 06/15/2009 02:48 PM, Michael S. Tsirkin wrote:
>> A slot needs to be configured in ACPI,
>>      
>
> Can we configure all possible 32 slots?
>    

That's what we do.  But one is always taken.  In the future, perhaps more.

>> and not be taken by onboard chips
>> (piix takes slot 0, for example).
>>      
>
> piix is the root complex, isn't it? Are there other examples? If not,
> we could teach management about the root complex being special ...
>    

We should just tell the user which slots are open.

-- 
error compiling committee.c: too many arguments to function