From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
qemu-arm@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
John Snow <jsnow@redhat.com>,
Dmitry Fleytman <dmitry.fleytman@gmail.com>,
Jason Wang <jasowang@redhat.com>, Stefan Weil <sw@weilnetz.de>,
Keith Busch <kbusch@kernel.org>, Klaus Jensen <its@irrelevant.dk>,
Peter Maydell <peter.maydell@linaro.org>,
Andrey Smirnov <andrew.smirnov@gmail.com>,
Paul Burton <paulburton@kernel.org>,
Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Yan Vugenfirer <yan@daynix.com>,
Yuri Benditovich <yuri.benditovich@daynix.com>
Subject: Re: [PATCH v8 01/17] hw/vfio/pci: Ensure MSI and MSI-X do not overlap
Date: Tue, 1 Nov 2022 15:44:34 +0100 [thread overview]
Message-ID: <b96f7ad7-e2b1-28a0-c1cd-5ee402de2ac1@linaro.org> (raw)
In-Reply-To: <20221101135749.4477-2-akihiko.odaki@daynix.com>
On 1/11/22 14:57, Akihiko Odaki wrote:
> pci_add_capability() checks whether capabilities overlap, and notifies
> its caller so that it can properly handle the case. However, in the
> most cases, the capabilities actually never overlap, and the interface
> incurred extra error handling code, which is often incorrect or
> suboptimal. For such cases, pci_add_capability() can simply abort the
> execution if the capabilities actually overlap since it should be a
> programming error.
>
> This change handles the other cases: hw/vfio/pci depends on the check to
> decide MSI and MSI-X capabilities overlap with another. As they are
> quite an exceptional and hw/vfio/pci knows much about PCI capabilities,
> adding code specific to the cases to hw/vfio/pci still results in less
> code than having error handling code everywhere in total.
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> hw/pci/pci.c | 34 ++++++++++++++++++++++------------
> hw/vfio/pci.c | 15 ++++++++++++++-
> include/hw/pci/pci.h | 3 +++
> 3 files changed, 39 insertions(+), 13 deletions(-)
> /*
> * On success, pci_add_capability() returns a positive value
> * that the offset of the pci capability.
> @@ -2523,7 +2542,6 @@ int pci_add_capability(PCIDevice *pdev, uint8_t cap_id,
> Error **errp)
> {
> uint8_t *config;
> - int i, overlapping_cap;
>
> if (!offset) {
> offset = pci_find_space(pdev, size);
> @@ -2534,17 +2552,9 @@ int pci_add_capability(PCIDevice *pdev, uint8_t cap_id,
> * depends on this check to verify that the device is not broken.
> * Should never trigger for emulated devices, but it's helpful
> * for debugging these. */
> - for (i = offset; i < offset + size; i++) {
> - overlapping_cap = pci_find_capability_at_offset(pdev, i);
> - if (overlapping_cap) {
> - error_setg(errp, "%s:%02x:%02x.%x "
> - "Attempt to add PCI capability %x at offset "
> - "%x overlaps existing capability %x at offset %x",
> - pci_root_bus_path(pdev), pci_dev_bus_num(pdev),
> - PCI_SLOT(pdev->devfn), PCI_FUNC(pdev->devfn),
> - cap_id, offset, overlapping_cap, i);
> - return -EINVAL;
> - }
> + pci_check_capability_overlap(pdev, cap_id, offset, size, errp);
> + if (errp) {
if (!pci_check_capability_overlap(...)) {
> + return -EINVAL;
> }
> }
next prev parent reply other threads:[~2022-11-01 15:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 13:57 [PATCH v8 00/17] pci: Abort if pci_add_capability fails Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 01/17] hw/vfio/pci: Ensure MSI and MSI-X do not overlap Akihiko Odaki
2022-11-01 14:35 ` Philippe Mathieu-Daudé
2022-11-01 14:44 ` Philippe Mathieu-Daudé [this message]
2022-11-01 13:57 ` [PATCH v8 02/17] pci: Allow to omit errp for pci_add_capability Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 03/17] hw/i386/amd_iommu: Omit " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 04/17] ahci: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 05/17] e1000e: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 06/17] eepro100: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 07/17] hw/nvme: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 08/17] msi: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 09/17] hw/pci/pci_bridge: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 10/17] pcie: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 11/17] pci/shpc: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 12/17] msix: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 13/17] pci/slotid: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 14/17] hw/pci-bridge/pcie_pci_bridge: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 15/17] hw/vfio/pci: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 16/17] virtio-pci: " Akihiko Odaki
2022-11-01 13:57 ` [PATCH v8 17/17] pci: Remove legacy errp from pci_add_capability Akihiko Odaki
2022-11-01 14:37 ` Philippe Mathieu-Daudé
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=b96f7ad7-e2b1-28a0-c1cd-5ee402de2ac1@linaro.org \
--to=philmd@linaro.org \
--cc=akihiko.odaki@daynix.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=andrew.smirnov@gmail.com \
--cc=dmitry.fleytman@gmail.com \
--cc=eduardo@habkost.net \
--cc=its@irrelevant.dk \
--cc=jasowang@redhat.com \
--cc=jsnow@redhat.com \
--cc=kbusch@kernel.org \
--cc=kraxel@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=paulburton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sw@weilnetz.de \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.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).