Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Scott Bauer <scott.bauer@intel.com>,
	linux-pci@vger.kernel.org, jonathan.derrick@intel.com,
	david.fugate@intel.com, bhelgaas@google.com
Subject: Re: [RESEND] PCI: vmd: Free up IRQs on suspend path
Date: Fri, 11 Aug 2017 15:32:50 -0400	[thread overview]
Message-ID: <20170811193250.GD7233@localhost.localdomain> (raw)
In-Reply-To: <20170811184924.GE17039@bhelgaas-glaptop.roam.corp.google.com>

On Fri, Aug 11, 2017 at 01:49:24PM -0500, Bjorn Helgaas wrote:
> On Fri, Aug 11, 2017 at 12:09:49PM -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 ...
> 
> From the "RESEND", I assume this is identical to the original posting.
> 
> I disposed of the original as "changes requested" because of Jon's
> comments.  Keith subsequently chimed in saying he thought it was OK
> as-is.  Keith, can I convert that to a formal ack from you?

Yes, I'm okay with this patch.

Acked-by: Keith Busch <keith.busch@intel.com>

 
> > Signed-off-by: Scott Bauer <scott.bauer@intel.com>
> > ---
> >  drivers/pci/host/vmd.c | 17 +++++++++++++++++
> >  1 file changed, 17 insertions(+)
> > 
> > diff --git a/drivers/pci/host/vmd.c b/drivers/pci/host/vmd.c
> > index 7e967a8784b2..ac643a3d0bf3 100644
> > --- a/drivers/pci/host/vmd.c
> > +++ b/drivers/pci/host/vmd.c
> > @@ -763,15 +763,32 @@ 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);
> > +	pci_disable_device(pdev);
> >  	return 0;
> >  }
> >  
> >  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;
> > +	}
> >  
> > +	pcim_enable_device(pdev);
> >  	pci_restore_state(pdev);
> >  	return 0;
> >  }
> > -- 
> > 2.11.0
> > 

  reply	other threads:[~2017-08-11 19:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11 18:09 [RESEND] PCI: vmd: Free up IRQs on suspend path Scott Bauer
2017-08-11 18:49 ` Bjorn Helgaas
2017-08-11 19:32   ` Keith Busch [this message]
2017-08-11 20:25 ` 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=20170811193250.GD7233@localhost.localdomain \
    --to=keith.busch@intel.com \
    --cc=bhelgaas@google.com \
    --cc=david.fugate@intel.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