From: Jason Baron <jbaron@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: yamahata@valinux.co.jp, alex.williamson@redhat.com,
mst@redhat.com, qemu-devel@nongnu.org, jan.kiszka@siemens.com
Subject: Re: [Qemu-devel] q35 chipset support
Date: Fri, 15 Jun 2012 13:57:00 -0400 [thread overview]
Message-ID: <20120615175700.GD8244@redhat.com> (raw)
In-Reply-To: <4FDA4683.6050809@codemonkey.ws>
On Thu, Jun 14, 2012 at 03:16:03PM -0500, Anthony Liguori wrote:
> On 06/14/2012 02:54 PM, Jason Baron wrote:
> >Hi,
> >
> >I recently updated Isaku Yamahata's q35 patches to work on the latest qemu and
> >seabios trees. On the qemu side, most of the changes revolved around updating
> >to use QOM and updates to the memory API. I was also able to drop quite a few
> >patches that had already been resolved by the current qemu tree.
> >
> >The trees seem pretty stable and can be found here:
> >
> >git://github.com/jibaron/q35-qemu.git
> >git://github.com/jibaron/q35-seabios.git
>
> I'm got the beginnings of a feature page started:
>
> http://wiki.qemu.org/Features/Q35
>
> The approach above will not work in a QOM world unfortunately. We
> need to do quite a bit of ground work before adding another chipset.
> The biggest task is converting devices to not require an ISA bus
> since ICH9 simply doesn't have an ISA bus.
>
Right, there is no h/w isa bus, but the LPC interface chip is modeled as an isa
bridge. So having an isa bus hanging off of it doesn't seem unreasonable. Unless
there is some more fundamental reason not do it this way?
It hows up in lspci as:
00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface
Controller (rev 02)
> You can hack things together to work without this, but the result is
> unmaintainable spaghetti (which is pretty close to what we already
> have today).
>
> Once the QOM bus support gets merged, I'm going to send out an ISA
> bus refactoring which gets most of the platform devices away from
> ISA..
>
> Regards,
>
> Anthony Liguori
>
next prev parent reply other threads:[~2012-06-15 17:57 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
2012-06-18 15:36 ` Andreas Färber
2012-06-18 15:45 ` Anthony Liguori
2012-06-15 17:57 ` Jason Baron [this message]
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=20120615175700.GD8244@redhat.com \
--to=jbaron@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=mst@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).