From: Marcel Apfelbaum <marcel@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com, zuban32s@gmail.com, cohuck@redhat.com
Subject: Re: [Qemu-devel] [PATCH] hw/pcie-pci-bridge: restrict to X86 and ARM
Date: Wed, 8 Nov 2017 19:02:35 +0200 [thread overview]
Message-ID: <6722cc03-9311-c19b-3f26-4f0cc41a1770@redhat.com> (raw)
In-Reply-To: <3722f599-31b4-adb6-270b-aff5819f1bd3@redhat.com>
On 08/11/2017 18:52, Thomas Huth wrote:
> On 08.11.2017 16:20, Marcel Apfelbaum wrote:
>> The PCIE-PCI bridge is specific to "pure" PCI systems
>
Hi Thomas,
> s/PCI/PCIe/ ?
>
In this context maybe it doesn't really matter,
but if I'll send a v2 I'll make the change, sure.
>> (on QEMU we have X86 and ARM), it does not make sense to
>> have if in other archs.
>>
>> Reported-by: Thomas Huth <thuth@redhat.com>
>> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
>> ---
>> default-configs/arm-softmmu.mak | 1 +
>> default-configs/i386-softmmu.mak | 1 +
>> default-configs/x86_64-softmmu.mak | 1 +
>> hw/pci-bridge/Makefile.objs | 3 ++-
>> 4 files changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/default-configs/arm-softmmu.mak b/default-configs/arm-softmmu.mak
>> index 5059d134c8..33934b1dc4 100644
>> --- a/default-configs/arm-softmmu.mak
>> +++ b/default-configs/arm-softmmu.mak
>> @@ -122,6 +122,7 @@ CONFIG_FSL_IMX25=y
>> CONFIG_IMX_I2C=y
>>
>> CONFIG_PCIE_PORT=y
>> +CONFIG_PCIE_PCI_BRIDGE=y
>
> Actually, why not simply use CONFIG_PCIE_PORT instead to determine
> whether the PCIe-to-PCI bridge should be included? The device only makes
> sense if there is a PCIe root port available on the system...
>
I thought about it, but then we should also change all the devices
that makes sense only if connected to PCIe Root Ports, like Intel
Upstream Ports (Switches) and maybe more. (otherwise people will
start asking why it is different.)
We could use CONFIG_PCIE_PCI_BRIDGE=CONFIG_PCIE_PORT or something
but it looks weird.
This is why I've chosen the "independent" config option.
But, to be fair, I have nothing against your suggestion,
let's see what others think.
Thanks for the review,
Marcel
> Thomas
>
next prev parent reply other threads:[~2017-11-08 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 15:20 [Qemu-devel] [PATCH] hw/pcie-pci-bridge: restrict to X86 and ARM Marcel Apfelbaum
2017-11-08 15:48 ` no-reply
2017-11-08 16:52 ` Thomas Huth
2017-11-08 17:02 ` Marcel Apfelbaum [this message]
2017-11-08 17:29 ` Cornelia Huck
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=6722cc03-9311-c19b-3f26-4f0cc41a1770@redhat.com \
--to=marcel@redhat.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=zuban32s@gmail.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).