From: Paolo Bonzini <pbonzini@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
mst@redhat.com, yamahata@valinux.co.jp
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Make i82801b11 and ioh3420 x86 only by default
Date: Wed, 18 Feb 2015 08:57:39 +0100 [thread overview]
Message-ID: <54E445F3.3070802@redhat.com> (raw)
In-Reply-To: <1424235596-29024-1-git-send-email-david@gibson.dropbear.id.au>
On 18/02/2015 05:59, David Gibson wrote:
> As PCI devices, the i82801b11 and ioh3420 devices could theoretically exist
> on any platform with a PCI bus. However in practice, they're Intel
> specific devices,
They can be used as a generic PCIe root port and PCIe-to-PCI bridge,
they're not Intel-specific as long as your firmware doesn't care about
the vendor and device id.
> that are very unlikely to appear on anything other than
> an x86. Therefore this patch gives them their own config options, enabled
> only for x86 targets by default.
I think it's quite likely that we'll use them, or at least ioh3420, on
any PCIe machine. So you probably want to add ioh3420 to arm-softmmu
and aarch64-softmmu as well. I don't know about i82801b11, but it
doesn't hurt to have it in ARM/AArch64 either.
Also, the same can be done for xio3130, so you can also limit that one
to x86 and ARM/Aarch64.
Paolo
next prev parent reply other threads:[~2015-02-18 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 4:59 [Qemu-devel] [PATCH] Make i82801b11 and ioh3420 x86 only by default David Gibson
2015-02-18 6:03 ` David Gibson
2015-02-18 7:57 ` Paolo Bonzini [this message]
2015-02-19 2:05 ` David Gibson
2015-02-19 3:45 ` Peter Maydell
2015-02-19 5:20 ` David Gibson
2015-02-19 10:30 ` Michael S. Tsirkin
2015-02-19 9:57 ` Paolo Bonzini
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=54E445F3.3070802@redhat.com \
--to=pbonzini@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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).