From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Marcel Apfelbaum <marcel@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/pci: ensure that only PCI/PCIe bridges can be attached to pxb/pxb-pcie devices
Date: Mon, 18 Jan 2016 19:16:21 +0100 [thread overview]
Message-ID: <569D2BF5.9050604@redhat.com> (raw)
In-Reply-To: <CAFEAcA-Gki8Afy1qp+ymKC1FA8KuESZMpM4BJnvoqka8Xx+S=A@mail.gmail.com>
On 01/18/16 19:08, Peter Maydell wrote:
> On 18 January 2016 at 15:27, Marcel Apfelbaum <marcel@redhat.com> wrote:
>> PCI devices can't be plugged directly into PCI extra root bridges
>> because their resources can't be computed by firmware before the ACPI
>> tables are loaded.
>>
>> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
>> ---
>>
>> Hi,
>>
>> This patch follows the discussion:
>> https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg01484.html
>
> Is it definitely the case that no current working command lines plug
> PCI devices directly into these things (including on platforms that
> don't have anything to do with ACPI at all) ?
No clue about "pxb-pcie", but re: "pxb", the documentation and examples
by Marcel (see: "docs/pci_expander_bridge.txt") will certainly continue
working, with this patch place. And, that text file is authoritative for
pxb, since Marcel (et al) wrote the code directly for the purposes
described in the txt.
(But I'll let Marcel answer too! :))
Thanks
Laszlo
next prev parent reply other threads:[~2016-01-18 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 15:27 [Qemu-devel] [PATCH] hw/pci: ensure that only PCI/PCIe bridges can be attached to pxb/pxb-pcie devices Marcel Apfelbaum
2016-01-18 18:02 ` Laszlo Ersek
2016-01-18 18:08 ` Peter Maydell
2016-01-18 18:16 ` Laszlo Ersek [this message]
2016-01-18 18:27 ` Peter Maydell
2016-01-19 8:04 ` Marcel Apfelbaum
2016-02-02 12:09 ` 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=569D2BF5.9050604@redhat.com \
--to=lersek@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).