From: Collin Walling <walling@linux.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Cornelia Huck" <cohuck@redhat.com>,
"open list:RISC-V" <qemu-riscv@nongnu.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Sagar Karandikar" <sagark@eecs.berkeley.edu>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Helge Deller" <deller@gmx.de>,
"Palmer Dabbelt" <palmer@sifive.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Artyom Tarasenko" <atar4qemu@gmail.com>,
"open list:S390" <qemu-s390x@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Alistair Francis" <Alistair.Francis@wdc.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-ppc <qemu-ppc@nongnu.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [qemu-s390x] [RFC PATCH 1/3] hw/Kconfig: PCI bus implies PCI_DEVICES
Date: Wed, 17 Jul 2019 10:54:29 -0400 [thread overview]
Message-ID: <87f07cd0-ebbc-3569-9070-5700e47d4af8@linux.ibm.com> (raw)
In-Reply-To: <633cc3f7-eb20-1bfe-03d2-e481be188eb1@redhat.com>
On 7/17/19 9:52 AM, Paolo Bonzini wrote:
> On 17/07/19 14:59, Collin Walling wrote:
>> On 7/16/19 11:04 AM, Thomas Huth wrote:
>>> On 16/07/2019 15.06, Markus Armbruster wrote:
>>>> Paolo Bonzini <pbonzini@redhat.com> writes:
>>>>
>>>>> On 15/07/19 18:12, Cornelia Huck wrote:
>>>>>>> Is it INTx vs. MSI vs. MSI-X?
>>>>>>
>>>>>> I think for s390x we need (INTx || MSI) vs MSI-X...
>>>>>
>>>>> I think MSI vs MSI-X is just how it's configured, not the actual
>>>>> behavior, so it should be irrelevant.
>>>>
>>>> My best guesses from confusing information, please correct
>>>> misunderstandings:
>>>>
>>>> 1. PCI devices need to support MSI or MSI-X to work with s390x.
>>>
>>> I think Cornelia mentioned that we might even require MSI-X there ...
>>> Collin (being listed as "S390 PCI" maintainer), can you confirm?
>>
>> MSI-X is mandatory for PCI devices in the s390 architecture.
>
> How are MSI and MSI-X distinguished?
>
> Paolo
>
PCI host plugging will check for the MSI-X capability on the
PCI device. If the MSI-X cap is missing, we fail device plugging.
We do not check for MSI. Only MSI-X.
Specifically, the capability is represented by PCI_CAP_ID_MSIX
in pci_regs.h
next prev parent reply other threads:[~2019-07-17 14:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 9:55 [Qemu-devel] [PATCH 0/3] hw/Kconfig: PCI & USB fixes Philippe Mathieu-Daudé
2019-07-15 9:55 ` [Qemu-devel] [RFC PATCH 1/3] hw/Kconfig: PCI bus implies PCI_DEVICES Philippe Mathieu-Daudé
2019-07-15 10:15 ` Thomas Huth
2019-07-15 10:19 ` Peter Maydell
2019-07-15 10:48 ` Thomas Huth
2019-07-15 10:56 ` [Qemu-devel] [qemu-s390x] " Cornelia Huck
2019-07-15 11:04 ` Philippe Mathieu-Daudé
2019-07-15 11:09 ` Cornelia Huck
2019-07-15 13:19 ` Thomas Huth
2019-07-15 13:38 ` Philippe Mathieu-Daudé
2019-07-15 13:49 ` Thomas Huth
2019-07-15 16:08 ` Markus Armbruster
2019-07-15 16:12 ` Cornelia Huck
2019-07-15 18:22 ` Paolo Bonzini
2019-07-16 13:06 ` Markus Armbruster
2019-07-16 15:04 ` Thomas Huth
2019-07-17 12:59 ` Collin Walling
2019-07-17 13:52 ` Paolo Bonzini
2019-07-17 14:54 ` Collin Walling [this message]
2019-07-17 15:04 ` Paolo Bonzini
2019-07-18 15:33 ` Cornelia Huck
2019-07-22 13:40 ` Markus Armbruster
2019-07-15 9:55 ` [Qemu-devel] [PATCH-for-4.2 2/3] hw/usb/Kconfig: Add CONFIG_USB_EHCI_PCI Philippe Mathieu-Daudé
2019-07-15 10:54 ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2019-07-15 11:03 ` Thomas Huth
2019-07-15 11:10 ` BALATON Zoltan
2019-07-15 11:19 ` Thomas Huth
2019-07-15 11:20 ` Paolo Bonzini
2019-07-15 11:01 ` [Qemu-devel] " Thomas Huth
2019-07-15 9:55 ` [Qemu-devel] [PATCH-for-4.1? 3/3] hw/usb/Kconfig: USB_XHCI_NEC requires USB_XHCI Philippe Mathieu-Daudé
2019-07-15 10:50 ` Thomas Huth
2019-07-15 11:21 ` [Qemu-devel] [PATCH 0/3] hw/Kconfig: PCI & USB fixes 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=87f07cd0-ebbc-3569-9070-5700e47d4af8@linux.ibm.com \
--to=walling@linux.ibm.com \
--cc=Alistair.Francis@wdc.com \
--cc=armbru@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=aurelien@aurel32.net \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=deller@gmx.de \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--cc=palmer@sifive.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=sagark@eecs.berkeley.edu \
--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).