From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: xen-devel@lists.xensource.com, Ian.Campbell@citrix.com,
Stefano.Stabellini@eu.citrix.com,
George Dunlap <george.dunlap@eu.citrix.com>,
Ian.Jackson@eu.citrix.com, wei.lui2@citrix.com,
qemu-devel@nongnu.org, Fabio Fantoni <fabio.fantoni@m2r.biz>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu
Date: Thu, 18 Jul 2013 14:35:00 +0200 [thread overview]
Message-ID: <51E7E0F4.5050006@redhat.com> (raw)
In-Reply-To: <51E7E039.70606@suse.de>
Il 18/07/2013 14:31, Andreas Färber ha scritto:
>> > I'm just curious, why is this so complicated? Is this likely to be
>> > fragile and break in the future?
> As pointed out previously, the bus=pci.0 bit will break with different
> PCI host bridges, such as the q35 machine existing today (-M q35 uses
> pcie.0 instead and it has been discussed to make q35 the default at some
> point). I had thus suggested to use a variable for the bus name to
> abstract it. For -M pc-i440fx-1.5 etc. pci.0 should continue to work.
I think if we ever made a PCIe machine the default, it would be
different from what today's q35. In particular it probably should
include a default DMI-to-PCI bridge, so as to make the command line
compatible with i440FX-based machines.
Paolo
next prev parent reply other threads:[~2013-07-18 12:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 10:22 [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu Fabio Fantoni
2013-07-12 11:06 ` George Dunlap
2013-07-12 11:15 ` Ian Campbell
2013-07-12 12:36 ` Fabio Fantoni
2013-07-12 15:33 ` George Dunlap
2013-07-15 9:10 ` Fabio Fantoni
2013-07-18 11:09 ` Ian Jackson
2013-07-18 11:13 ` George Dunlap
2013-07-18 11:31 ` Anthony Liguori
2013-07-18 12:15 ` Ian Jackson
2013-07-18 12:31 ` Andreas Färber
2013-07-18 12:35 ` Paolo Bonzini [this message]
2013-08-14 10:30 ` Fabio Fantoni
2013-09-11 10:14 ` Fabio Fantoni
2013-09-11 10:19 ` Ian Campbell
2013-09-11 11:38 ` Fabio Fantoni
2013-09-11 13:19 ` Fabio Fantoni
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=51E7E0F4.5050006@redhat.com \
--to=pbonzini@redhat.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=fabio.fantoni@m2r.biz \
--cc=george.dunlap@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=wei.lui2@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).