From: Keith Busch <keith.busch@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Scott Bauer <scott.bauer@intel.com>,
bhelgaas@google.com, linux-pci@vger.kernel.org,
jonathan.derrick@intel.com
Subject: Re: [PATCH] PCI: vmd: Free up IRQs on suspend path
Date: Mon, 14 Aug 2017 14:15:47 -0400 [thread overview]
Message-ID: <20170814181547.GF7233@localhost.localdomain> (raw)
In-Reply-To: <20170814180652.GA32525@bhelgaas-glaptop.roam.corp.google.com>
On Mon, Aug 14, 2017 at 01:06:52PM -0500, Bjorn Helgaas wrote:
> On Fri, Aug 11, 2017 at 02:54:32PM -0600, Scott Bauer wrote:
> > This patch frees up the IRQs we request on the suspend path,
> > and reallocates them on the resume path.
> >
> > Fixes:
> > [ 559.964386] CPU 111 disable failed: CPU has 9 vectors assigned and there are only 0 available.
> > [ 559.966824] Error taking CPU111 down: -34
> > [ 559.966825] Non-boot CPUs are not disabled
> > [ 559.966826] Enabling non-boot CPUs ...
> >
> > Signed-off-by: Scott Bauer <scott.bauer@intel.com>
>
> Keith acked the previous version (which contained the enable/disable),
> but since this is different, I'll wait for his ack again.
Thanks for checking. This is actually the patch that was intended for
submission.
Acked-by: Keith Busch <keith.busch@intel.com>
> > ---
> > drivers/pci/host/vmd.c | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/drivers/pci/host/vmd.c b/drivers/pci/host/vmd.c
> > index 7e967a8784b2..4fe1756af010 100644
> > --- a/drivers/pci/host/vmd.c
> > +++ b/drivers/pci/host/vmd.c
> > @@ -763,6 +763,11 @@ static void vmd_remove(struct pci_dev *dev)
> > static int vmd_suspend(struct device *dev)
> > {
> > struct pci_dev *pdev = to_pci_dev(dev);
> > + struct vmd_dev *vmd = pci_get_drvdata(pdev);
> > + int i;
> > +
> > + for (i = 0; i < vmd->msix_count; i++)
> > + devm_free_irq(dev, pci_irq_vector(pdev, i), &vmd->irqs[i]);
> >
> > pci_save_state(pdev);
> > return 0;
> > @@ -771,6 +776,16 @@ static int vmd_suspend(struct device *dev)
> > static int vmd_resume(struct device *dev)
> > {
> > struct pci_dev *pdev = to_pci_dev(dev);
> > + struct vmd_dev *vmd = pci_get_drvdata(pdev);
> > + int err, i;
> > +
> > + for (i = 0; i < vmd->msix_count; i++) {
> > + err = devm_request_irq(dev, pci_irq_vector(pdev, i),
> > + vmd_irq, IRQF_NO_THREAD,
> > + "vmd", &vmd->irqs[i]);
> > + if (err)
> > + return err;
> > + }
> >
> > pci_restore_state(pdev);
> > return 0;
> > --
> > 2.11.0
> >
next prev parent reply other threads:[~2017-08-14 18:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 20:54 [PATCH] PCI: vmd: Free up IRQs on suspend path Scott Bauer
2017-08-14 18:06 ` Bjorn Helgaas
2017-08-14 18:15 ` Keith Busch [this message]
2017-08-14 20:30 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2017-07-20 20:28 Scott Bauer
2017-07-26 2:15 ` Jon Derrick
2017-07-20 21:34 ` Scott Bauer
2017-07-26 2:36 ` Jon Derrick
2017-07-20 21:56 ` Scott Bauer
2017-07-20 22:41 ` Keith Busch
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=20170814181547.GF7233@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jonathan.derrick@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=scott.bauer@intel.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).