From: Alexander Gordeev <agordeev@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] portdrv: Use pci_enable_msix_range() instead of pci_enable_msix()
Date: Thu, 20 Feb 2014 13:44:01 +0100 [thread overview]
Message-ID: <20140220124400.GA8198@dhcp-26-207.brq.redhat.com> (raw)
In-Reply-To: <CAErSpo7xWe6n3Nk3Aatik4tfSHQLQehf3WELqD=q1oTmXYVVuw@mail.gmail.com>
On Wed, Feb 19, 2014 at 03:09:41PM -0700, Bjorn Helgaas wrote:
> On Wed, Feb 19, 2014 at 3:15 AM, Alexander Gordeev <agordeev@redhat.com> wrote:
> > As result of deprecation of MSI-X/MSI enablement functions
> > pci_enable_msix() and pci_enable_msi_block() all drivers
> > using these two interfaces need to be updated to use the
> > new pci_enable_msi_range() and pci_enable_msix_range()
> > interfaces.
> >
> > Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
> > Cc: Bjorn Helgaas <bhelgaas@google.com>
> > Cc: linux-pci@vger.kernel.org
> > ---
> > drivers/pci/pcie/portdrv_core.c | 17 ++++++++++-------
> > 1 files changed, 10 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/pci/pcie/portdrv_core.c b/drivers/pci/pcie/portdrv_core.c
> > index 986f8ea..4e46eca 100644
> > --- a/drivers/pci/pcie/portdrv_core.c
> > +++ b/drivers/pci/pcie/portdrv_core.c
> > @@ -99,8 +99,9 @@ static int pcie_port_enable_msix(struct pci_dev *dev, int *vectors, int mask)
> > for (i = 0; i < nr_entries; i++)
> > msix_entries[i].entry = i;
> >
> > - status = pci_enable_msix(dev, msix_entries, nr_entries);
> > - if (status)
> > + status = pci_enable_msix_range(dev,
> > + msix_entries, nr_entries, nr_entries);
>
> This is a place we could use pci_enable_msix_exact(), isn't it? (Also below.)
Yes, absolutely.
I posted it (and other updates) as is, since I understood
pci_enable_msix_exact() is not going to make it into 3.14. Was I wrong here?
I think more time in testing with either pci_enable_msix_range() or
pci_enable_msix_exact() is good. And a follow-up switch from
pci_enable_msix_range() to pci_enable_msix_exact() should be easy eigher.
What do you think is the best course of action now?
> > + if (status < 0)
> > goto Exit;
> >
> > for (i = 0; i < PCIE_PORT_DEVICE_MAXSERVICES; i++)
> > @@ -159,21 +160,23 @@ static int pcie_port_enable_msix(struct pci_dev *dev, int *vectors, int mask)
> > idx[PCIE_PORT_SERVICE_AER_SHIFT] = i;
> > }
> >
> > + status = 0;
> > +
> > /*
> > * If nvec is equal to the allocated number of entries, we can just use
> > * what we have. Otherwise, the port has some extra entries not for the
> > * services we know and we need to work around that.
> > */
> > - if (nvec == nr_entries) {
> > - status = 0;
> > - } else {
> > + if (nvec != nr_entries) {
> > /* Drop the temporary MSI-X setup */
> > pci_disable_msix(dev);
> >
> > /* Now allocate the MSI-X vectors for real */
> > - status = pci_enable_msix(dev, msix_entries, nvec);
> > - if (status)
> > + nvec = pci_enable_msix_range(dev, msix_entries, nvec, nvec);
> > + if (nvec < 0) {
> > + status = nvec;
> > goto Exit;
> > + }
> > }
> >
> > for (i = 0; i < PCIE_PORT_DEVICE_MAXSERVICES; i++)
> > --
> > 1.7.7.6
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Regards,
Alexander Gordeev
agordeev@redhat.com
next prev parent reply other threads:[~2014-02-20 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 10:15 [PATCH] portdrv: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-19 22:09 ` Bjorn Helgaas
2014-02-20 12:44 ` Alexander Gordeev [this message]
2014-02-20 14:51 ` Bjorn Helgaas
2014-02-21 16:24 ` [PATCH v2] portdrv: Use pci_enable_msix_exact() " Alexander Gordeev
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=20140220124400.GA8198@dhcp-26-207.brq.redhat.com \
--to=agordeev@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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).