From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Cc: imammedo@redhat.com, rth@twiddle.net, kraxel@redhat.com,
ehabkost@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V2 0/4] hw/pcie: Multi-root support for Q35
Date: Mon, 16 Nov 2015 10:56:39 +0100 [thread overview]
Message-ID: <5649A857.406@redhat.com> (raw)
In-Reply-To: <5649A770.5070908@redhat.com>
On 16/11/2015 10:52, Marcel Apfelbaum wrote:
> On 11/16/2015 10:40 AM, Paolo Bonzini wrote:
>>
>>
>> On 15/11/2015 16:39, Marcel Apfelbaum wrote:
>>> Addressed Gerd Hoffmann comments:
>>> - Added x-enable-internal-bridge compat property to keep the PCI
>>> bridge for older machine to avoid breaking migration.
>>
>> This will break PXB command lines written for "-M pc" in QEMU <= 2.5.
>> Technically there's no prohibition against doing so, but we've never
>> done it; I'm not sure why we should start doing so now.
>
> Hi Paolo,
>
> Can you please explain how does it break the command line?
>
> For QEMU < 2.5 we automatically have the x-enable-internal-bridge
> compat property "on"
> so the command line remains the same.
>
> For QEMU >= 2.5 is "off" by default and the bridge disappear, without
> command line changes.
If you were using "-M pc", and you expected "-device" to place things
under the PCI-to-PCI bridge, that command line will not work anymore I
think.
Management tools can work around it. They can always set the new
property to off---which by the way means it should not be "x"
prefixed---and assume the PCI-to-PCI bridge is there if the property
doesn't exist. But it's inconvenient, and we try to avoid lockstep
changes to QEMU and management.
Paolo
>> Can we have two devices, on for a PCI expander bridge and one for a PCIe
>> expander bridge?
>
> Gerd also asked for this, OK, I am going for it.
>
> Thanks,
> Marcel
>
>>
>> Paolo
>>
>
next prev parent reply other threads:[~2015-11-16 9:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 15:39 [Qemu-devel] [PATCH V2 0/4] hw/pcie: Multi-root support for Q35 Marcel Apfelbaum
2015-11-15 15:39 ` [Qemu-devel] [PATCH V2 1/4] hw/pxb: remove the built-in pci bridge Marcel Apfelbaum
2015-11-15 15:39 ` [Qemu-devel] [PATCH V2 2/4] hw/acpi: merge pxb adjacent memory/IO ranges Marcel Apfelbaum
2015-11-15 15:39 ` [Qemu-devel] [PATCH V2 3/4] hw/pc: query both q35 and i440fx bus Marcel Apfelbaum
2015-11-16 18:26 ` Eduardo Habkost
2015-11-17 10:29 ` Marcel Apfelbaum
2015-11-15 15:39 ` [Qemu-devel] [PATCH V2 4/4] hw/pxb: add support for PCIe Marcel Apfelbaum
2015-11-16 8:40 ` [Qemu-devel] [PATCH V2 0/4] hw/pcie: Multi-root support for Q35 Paolo Bonzini
2015-11-16 9:52 ` Marcel Apfelbaum
2015-11-16 9:56 ` Paolo Bonzini [this message]
2015-11-16 10:02 ` Marcel Apfelbaum
2015-11-16 10:03 ` Paolo Bonzini
2015-11-16 10:10 ` Marcel Apfelbaum
2015-11-16 10:11 ` Paolo Bonzini
2015-11-16 10:34 ` Marcel Apfelbaum
2015-11-16 10:37 ` Michael S. Tsirkin
2015-11-16 10:39 ` Marcel Apfelbaum
2015-11-16 10:59 ` Michael S. Tsirkin
2015-11-16 11:37 ` Marcel Apfelbaum
2015-11-16 13:30 ` Paolo Bonzini
2015-11-19 15:05 ` Laine Stump
2015-11-17 8:15 ` Markus Armbruster
2015-11-17 10:42 ` Marcel Apfelbaum
2015-11-17 12:26 ` Markus Armbruster
2015-11-17 13:49 ` Marcel Apfelbaum
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=5649A857.406@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.