From: Bjorn Helgaas <helgaas@kernel.org>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: bhelgaas@google.com, nathan@kernel.org, ndesaulniers@google.com,
trix@redhat.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
tglx@linutronix.de, kevin.tian@intel.com, darwi@linutronix.de
Subject: Re: [PATCH] PCI: Fix build error when CONFIG_PCI_MSI disabled
Date: Tue, 14 Feb 2023 16:24:00 -0600 [thread overview]
Message-ID: <20230214222400.GA3089902@bhelgaas> (raw)
In-Reply-To: <158e40e1cfcfc58ae30ecb2bbfaf86e5bba7a1ef.1675978686.git.reinette.chatre@intel.com>
On Thu, Feb 09, 2023 at 01:49:00PM -0800, Reinette Chatre wrote:
> pci_msix_alloc_irq_at() and pci_msix_free_irq() are not
> declared when CONFIG_PCI_MSI is disabled.
>
> Users of these two calls do not yet exist but when users
> do appear (shown below is an attempt to use the new API
> in vfio-pci) the following errors will be encountered when
> compiling with CONFIG_PCI_MSI disabled:
> drivers/vfio/pci/vfio_pci_intrs.c:461:4: error: implicit declaration of\
> function 'pci_msix_free_irq' is invalid in C99\
> [-Werror,-Wimplicit-function-declaration]
> pci_msix_free_irq(pdev, msix_map);
> ^
> drivers/vfio/pci/vfio_pci_intrs.c:461:4: note: did you mean 'pci_ims_free_irq'?
> include/linux/pci.h:2516:6: note: 'pci_ims_free_irq' declared here
> void pci_ims_free_irq(struct pci_dev *pdev, struct msi_map map);
> ^
> drivers/vfio/pci/vfio_pci_intrs.c:511:15: error: implicit declaration of\
> function 'pci_msix_alloc_irq_at' is invalid in C99\
> [-Werror,-Wimplicit-function-declaration]
> msix_map = pci_msix_alloc_irq_at(pdev, vector, NULL);
> ^
> drivers/vfio/pci/vfio_pci_intrs.c:511:15: note: did you mean 'pci_ims_alloc_irq'?
> include/linux/pci.h:2514:16: note: 'pci_ims_alloc_irq' declared here
> struct msi_map pci_ims_alloc_irq(struct pci_dev *pdev,\
> union msi_instance_cookie *icookie,
>
> Provide definitions for pci_msix_alloc_irq_at() and pci_msix_free_irq() in
> preparation for users that need to compile when CONFIG_PCI_MSI is
> disabled.
I think this should have a "Fixes:" tag to connect it with the commit
that added pci_msix_alloc_irq_at() and pci_msix_free_irq().
Looks like 34026364df8e ("PCI/MSI: Provide post-enable dynamic
allocation interfaces for MSI-X").
Thomas merged 34026364df8e, so it would be best if he took the fixup
as well.
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
> ---
>
> checkpatch.pl warns about the usage of -ENOSYS but it does appear
> to be the custom.
>
> include/linux/pci.h | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index adffd65e84b4..448482d1c4fe 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -1621,6 +1621,19 @@ pci_alloc_irq_vectors(struct pci_dev *dev, unsigned int min_vecs,
> flags, NULL);
> }
>
> +static inline struct msi_map
> +pci_msix_alloc_irq_at(struct pci_dev *dev, unsigned int index,
> + const struct irq_affinity_desc *affdesc)
> +{
> + struct msi_map map = { .index = -ENOSYS };
> +
> + return map;
> +}
> +
> +static inline void pci_msix_free_irq(struct pci_dev *pdev, struct msi_map map)
> +{
> +}
> +
> static inline void pci_free_irq_vectors(struct pci_dev *dev)
> {
> }
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-02-14 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 21:49 [PATCH] PCI: Fix build error when CONFIG_PCI_MSI disabled Reinette Chatre
2023-02-10 5:12 ` Tian, Kevin
2023-02-10 20:45 ` ALOK TIWARI
2023-02-10 21:12 ` Reinette Chatre
2023-02-11 5:05 ` [External] : " ALOK TIWARI
2023-02-13 18:46 ` Thomas Gleixner
2023-02-14 22:24 ` Bjorn Helgaas [this message]
2023-02-14 22:44 ` Reinette Chatre
2023-02-14 23:02 ` Thomas Gleixner
2023-02-14 23:14 ` Bjorn Helgaas
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=20230214222400.GA3089902@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=darwi@linutronix.de \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=trix@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