From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Isaku Yamahata <yamahata@valinux.co.jp>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Make i82801b11 and ioh3420 x86 only by default
Date: Thu, 19 Feb 2015 11:30:33 +0100 [thread overview]
Message-ID: <20150219103033.GB24587@redhat.com> (raw)
In-Reply-To: <20150219052036.GE7312@voom.redhat.com>
On Thu, Feb 19, 2015 at 04:20:36PM +1100, David Gibson wrote:
>
> On Thu, Feb 19, 2015 at 12:45:23PM +0900, Peter Maydell wrote:
> > On 18 February 2015 at 16:57, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > > On 18/02/2015 05:59, David Gibson wrote:
> > >> 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.
> >
> > What's the motivation for narrowing these down to particular
> > configs anyway?
>
> Simply to avoid probably-irrelevant devices showing up in qemu -device
> ?
And make the binary smaller.
--
MST
next prev parent reply other threads:[~2015-02-19 10:30 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
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 [this message]
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=20150219103033.GB24587@redhat.com \
--to=mst@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.