From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:36673)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1Sgd4u-0002HU-O9
	for qemu-devel@nongnu.org; Mon, 18 Jun 2012 10:37:21 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1Sgd4q-0004x5-3V
	for qemu-devel@nongnu.org; Mon, 18 Jun 2012 10:37:16 -0400
Received: from mx1.redhat.com ([209.132.183.28]:16616)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1Sgd4p-0004ww-Rr
	for qemu-devel@nongnu.org; Mon, 18 Jun 2012 10:37:12 -0400
Date: Mon, 18 Jun 2012 17:37:06 +0300
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20120618143706.GC26540@redhat.com>
References: <20120614195458.GB8244@redhat.com> <4FDA4683.6050809@codemonkey.ws>
	<m3pq91m4xc.fsf@blackfin.pond.sub.org>
	<4FDB77C9.6020901@codemonkey.ws>
	<20120618142043.GA26540@redhat.com>
	<4FDF39B3.9050806@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FDF39B3.9050806@codemonkey.ws>
Subject: Re: [Qemu-devel] q35 chipset support
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: jan.kiszka@siemens.com, Jason Baron <jbaron@redhat.com>, qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>, yamahata@valinux.co.jp, alex.williamson@redhat.com

On Mon, Jun 18, 2012 at 09:22:43AM -0500, Anthony Liguori wrote:
> On 06/18/2012 09:20 AM, Michael S. Tsirkin wrote:
> >On Fri, Jun 15, 2012 at 12:58:33PM -0500, Anthony Liguori wrote:
> >>So we need to fix our topological representation of platform devices
> >>before we start adding more complex chipsets.  Otherwise, we're
> >>going to end up in a bad situation in the near future.
> >
> >OTOH more in-tree examples especially for x86 will keep us
> >honest: help make sure abstractions make sense,
> >and prevent people from special casing piix because
> >this is the prevalent platform for kvm ATM.
> 
> Yes, more in-tree *correct* examples.  I'm very much in favor of merging q35.
> 
> Regards,
> 
> Anthony Liguori

But is there a way to build a correct chipset right now?
Or is this blocked waiting for more infrastructure
to get merged?

-- 
MST