From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Cédric Le Goater" <clg@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-s390x@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Akihiko Odaki <akihiko.odaki@daynix.com>,
Jason Wang <jasowang@redhat.com>,
Dmitry Fleytman <dmitry.fleytman@gmail.com>,
Sriram Yagnaraman <sriram.yagnaraman@est.tech>,
Sebastian Mitterle <smitterl@redhat.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PATCH v4] kconfig: Add PCIe devices to s390x machines
Date: Wed, 12 Jul 2023 12:48:24 +0200 [thread overview]
Message-ID: <007f4ae2-c39b-70ad-9e23-9edd543e393c@linaro.org> (raw)
In-Reply-To: <20230712080146.839113-1-clg@redhat.com>
Hi Cédric,
On 12/7/23 10:01, Cédric Le Goater wrote:
> It is useful to extend the number of available PCIe devices to KVM guests
> for passthrough scenarios and also to expose these models to a different
> (big endian) architecture. Introduce a new config PCIE_DEVICES to select
> models, Intel Ethernet adapters and one USB controller. These devices all
> support MSI-X which is a requirement on s390x as legacy INTx are not
> supported.
>
> Cc: Matthew Rosato <mjrosato@linux.ibm.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
> ---
>
> There could be a more general use of PCIE_DEVICES
>
> v4: Introduce PCIE_DEVICES
> v3: PCI -> PCI_EXPRESS
> v2: select -> imply
>
> configs/devices/s390x-softmmu/default.mak | 1 +
> hw/net/Kconfig | 4 ++--
> hw/pci/Kconfig | 3 +++
> hw/s390x/Kconfig | 3 ++-
> hw/usb/Kconfig | 2 +-
> 5 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/configs/devices/s390x-softmmu/default.mak b/configs/devices/s390x-softmmu/default.mak
> index f2287a133f36..2d5ff476e32a 100644
> --- a/configs/devices/s390x-softmmu/default.mak
> +++ b/configs/devices/s390x-softmmu/default.mak
> @@ -7,6 +7,7 @@
> #CONFIG_VFIO_CCW=n
> #CONFIG_VIRTIO_PCI=n
> #CONFIG_WDT_DIAG288=n
> +#CONFIG_PCIE_DEVICE=n
>
> # Boards:
> #
> diff --git a/hw/net/Kconfig b/hw/net/Kconfig
> index 98e00be4f937..7fcc0d7faa29 100644
> --- a/hw/net/Kconfig
> +++ b/hw/net/Kconfig
> @@ -41,12 +41,12 @@ config E1000_PCI
>
> config E1000E_PCI_EXPRESS
> bool
> - default y if PCI_DEVICES
> + default y if PCI_DEVICES || PCIE_DEVICES
There seems to be a pre-existing bug, shouldn't this be
default y if PCIE_DEVICES
?
(Cc'ing maintainers)
> depends on PCI_EXPRESS && MSI_NONBROKEN
>
> config IGB_PCI_EXPRESS
> bool
> - default y if PCI_DEVICES
> + default y if PCI_DEVICES || PCIE_DEVICES
Similarly:
default y if PCIE_DEVICES
> depends on PCI_EXPRESS && MSI_NONBROKEN
>
> config RTL8139_PCI
> diff --git a/hw/pci/Kconfig b/hw/pci/Kconfig
> index 77f8b005ffb1..fe70902cd821 100644
> --- a/hw/pci/Kconfig
> +++ b/hw/pci/Kconfig
> @@ -8,6 +8,9 @@ config PCI_EXPRESS
> config PCI_DEVICES
> bool
>
> +config PCIE_DEVICES
> + bool
> +
> config MSI_NONBROKEN
> # selected by interrupt controllers that do not support MSI,
> # or support it and have a good implementation. See commit
> diff --git a/hw/s390x/Kconfig b/hw/s390x/Kconfig
> index 454e0ff4b613..4c068d7960b9 100644
> --- a/hw/s390x/Kconfig
> +++ b/hw/s390x/Kconfig
> @@ -5,7 +5,8 @@ config S390_CCW_VIRTIO
> imply VFIO_AP
> imply VFIO_CCW
> imply WDT_DIAG288
> - select PCI
> + imply PCIE_DEVICES
> + select PCI_EXPRESS
I'm confused, TYPE_S390_PCI_HOST_BRIDGE exposes a PCI bus...
At a minimum you'd need:
-- >8 --
static const TypeInfo s390_pcihost_info = {
.name = TYPE_S390_PCI_HOST_BRIDGE,
- .parent = TYPE_PCI_HOST_BRIDGE,
+ .parent = TYPE_PCIE_HOST_BRIDGE,
.instance_size = sizeof(S390pciState),
.class_init = s390_pcihost_class_init,
.interfaces = (InterfaceInfo[]) {
---
Actually I can see:
if (s390_pci_msix_init(pbdev) && !pbdev->interp) {
error_setg(errp, "MSI-X support is mandatory "
"in the S390 architecture");
return;
}
So this must be PCIe, not legacy PCI, right?
> diff --git a/hw/usb/Kconfig b/hw/usb/Kconfig
> index 0ec6def4b8b8..0f486764ed69 100644
> --- a/hw/usb/Kconfig
> +++ b/hw/usb/Kconfig
> @@ -36,7 +36,7 @@ config USB_XHCI
>
> config USB_XHCI_PCI
> bool
> - default y if PCI_DEVICES
> + default y if PCI_DEVICES || PCIE_DEVICES
TYPE_XHCI_PCI inherits TYPE_PCI_DEVICE and implements
INTERFACE_PCIE_DEVICE, so this is OK.
> depends on PCI
> select USB_XHCI
>
next prev parent reply other threads:[~2023-07-12 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 8:01 [PATCH v4] kconfig: Add PCIe devices to s390x machines Cédric Le Goater
2023-07-12 10:48 ` Philippe Mathieu-Daudé [this message]
2023-07-12 17:03 ` Cédric Le Goater
2023-07-12 22:23 ` Akihiko Odaki
2023-07-12 12:11 ` Paolo Bonzini
2023-07-12 12:57 ` Thomas Huth
2023-07-12 15:43 ` 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=007f4ae2-c39b-70ad-9e23-9edd543e393c@linaro.org \
--to=philmd@linaro.org \
--cc=akihiko.odaki@daynix.com \
--cc=clg@redhat.com \
--cc=cohuck@redhat.com \
--cc=dmitry.fleytman@gmail.com \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=smitterl@redhat.com \
--cc=sriram.yagnaraman@est.tech \
--cc=thuth@redhat.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).