From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Cédric Le Goater" <clg@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, Thomas Huth <thuth@redhat.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>
Subject: Re: [PATCH v2] kconfig: Add PCIe devices to s390x machines
Date: Tue, 4 Jul 2023 15:33:57 +0200 [thread overview]
Message-ID: <bf100be6-2b22-f45d-3479-f8ce50cfdf76@linaro.org> (raw)
In-Reply-To: <149fdc25-f88d-67f5-f409-8ea2299e41ef@redhat.com>
On 4/7/23 14:32, Cédric Le Goater wrote:
> On 7/4/23 14:09, Philippe Mathieu-Daudé wrote:
>> On 4/7/23 14:01, Cédric Le Goater wrote:
>>> It is useful to extend the number of available PCI devices to KVM guests
>>> for passthrough scenarios and also to expose these models to a different
>>> (big endian) architecture. Include models for Intel Ethernet adapters
>>> and one USB controller, which all support MSI-X. Devices only supporting
>>> INTx won't work on s390x.
>>>
>>> Signed-off-by: Cédric Le Goater <clg@redhat.com>
>>> ---
>>>
>>> Tested under KVM as a machine device, under KVM nested as a
>>> passthrough
>>> device
>>>
>>> hw/s390x/Kconfig | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/hw/s390x/Kconfig b/hw/s390x/Kconfig
>>> index 5e7d8a2bae8b..7a82c58cdf6e 100644
>>> --- a/hw/s390x/Kconfig
>>> +++ b/hw/s390x/Kconfig
>>> @@ -10,3 +10,7 @@ config S390_CCW_VIRTIO
>>> select SCLPCONSOLE
>>> select VIRTIO_CCW
>>> select MSI_NONBROKEN
>>> + imply PCI_EXPRESS
>>
>> No, PCIe is a bus, which is implemented in s390-pci-bus.c;
>> S390_CCW_VIRTIO exposes this bus, so we Kconfig SELECT it.
>>
>>> + imply E1000E_PCI_EXPRESS
>>> + imply IGB_PCI_EXPRESS
>>> + imply USB_XHCI_PCI
>>
>> These are devices you can plug on a PCIe bus, so Kconfig
>> IMPLY is correct.
>
> If I understand correctly, this should be ?
>
> @@ -5,8 +5,11 @@ config S390_CCW_VIRTIO
> imply VFIO_AP
> imply VFIO_CCW
> imply WDT_DIAG288
> - select PCI
> + select PCI_EXPRESS
> select S390_FLIC
> select SCLPCONSOLE
> select VIRTIO_CCW
> select MSI_NONBROKEN
> + imply E1000E_PCI_EXPRESS
> + imply IGB_PCI_EXPRESS
> + imply USB_XHCI_PCI
This is how I'd write this patch. Note I have zero knowledge of zPCI.
next prev parent reply other threads:[~2023-07-04 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 12:01 [PATCH v2] kconfig: Add PCIe devices to s390x machines Cédric Le Goater
2023-07-04 12:09 ` Philippe Mathieu-Daudé
2023-07-04 12:32 ` Cédric Le Goater
2023-07-04 13:33 ` Philippe Mathieu-Daudé [this message]
2023-07-05 14:54 ` Matthew Rosato
2023-07-05 15:20 ` Cédric Le Goater
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=bf100be6-2b22-f45d-3479-f8ce50cfdf76@linaro.org \
--to=philmd@linaro.org \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--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).