From: "Michael S. Tsirkin" <mst@redhat.com>
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
Subject: Re: [Qemu-devel] q35 chipset support
Date: Mon, 18 Jun 2012 17:37:06 +0300 [thread overview]
Message-ID: <20120618143706.GC26540@redhat.com> (raw)
In-Reply-To: <4FDF39B3.9050806@codemonkey.ws>
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
next prev parent reply other threads:[~2012-06-18 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 19:54 [Qemu-devel] q35 chipset support Jason Baron
2012-06-14 20:16 ` Anthony Liguori
2012-06-15 7:04 ` Markus Armbruster
2012-06-15 17:58 ` Anthony Liguori
2012-06-17 8:25 ` Michael S. Tsirkin
2012-06-18 14:16 ` Anthony Liguori
2012-06-18 14:35 ` Michael S. Tsirkin
2012-06-18 15:15 ` Anthony Liguori
2012-06-18 16:04 ` Jason Baron
2012-06-18 13:51 ` Markus Armbruster
2012-06-18 14:05 ` Anthony Liguori
2012-06-18 20:36 ` Jason Baron
2012-06-18 21:15 ` Anthony Liguori
2012-06-18 14:20 ` Michael S. Tsirkin
2012-06-18 14:22 ` Anthony Liguori
2012-06-18 14:37 ` Michael S. Tsirkin [this message]
2012-06-18 15:36 ` Andreas Färber
2012-06-18 15:45 ` Anthony Liguori
2012-06-15 17:57 ` Jason Baron
2012-06-15 17:59 ` Anthony Liguori
2012-06-18 13:52 ` Markus Armbruster
2012-06-18 14:38 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120618143706.GC26540@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jbaron@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).