From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
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 09:16:24 -0500 [thread overview]
Message-ID: <4FDF3838.6050608@codemonkey.ws> (raw)
In-Reply-To: <20120617082501.GA28089@redhat.com>
On 06/17/2012 03:25 AM, Michael S. Tsirkin wrote:
> On Fri, Jun 15, 2012 at 12:58:33PM -0500, Anthony Liguori wrote:
>> The Q35 is much more sophisticated. The PCI-e complex itself can
>> present interesting topologies and the legacy PCI bus sits within
>> the PCI-e complex.
>
> Ah, so we can mix in PCI as well? Cool. How does
> such a mixed topology look?
It does, but I'm having a really hard time deciphering the spec here. Here's
what it says:
"The ICH9 PCI interface provides a 33 MHz, Revision 2.3 implementation. The ICH9
integrates a PCI arbiter that supports up to four external PCI bus masters in
addition to the internal ICH9 requests. This allows for combinations of up to
four PCI down devices and PCI slots."
So my interpretation of this is that it provides the ability to expose legacy
PCI slots. I can't get a reading though on how this shows up in the PCI
topology though.
It sounds like it would show up as a separate PCI domain.
Regards,
Anthony Liguori
>
next prev parent reply other threads:[~2012-06-18 14:16 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 [this message]
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
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=4FDF3838.6050608@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jbaron@redhat.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).