From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
mst@redhat.com
Subject: Re: [RFC PATCH] PCI: Disable MSI/MSI-X only if device is shutdown
Date: Fri, 13 Mar 2015 07:21:04 +0800 [thread overview]
Message-ID: <20150312232104.GA32054@ad.nay.redhat.com> (raw)
In-Reply-To: <5501BCF7.9080004@redhat.com>
On Thu, 03/12 17:21, Paolo Bonzini wrote:
> On 12/03/2015 06:21, Fam Zheng wrote:
> > If the device doesn't support shutdown, disabling interrupts may cause
> > trouble. For example, virtio-scsi-pci doesn't implement shutdown, and
> > after we disable MSI-X, futher notifications from device will be
> > delivered to IRQ, which is unexpected. This IRQ will not be cleared, and
> > may prevent us from making progress, by keep triggering interrupts.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > drivers/pci/pci-driver.c | 7 ++++---
> > 1 file changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> > index 3cb2210..fb29c96 100644
> > --- a/drivers/pci/pci-driver.c
> > +++ b/drivers/pci/pci-driver.c
> > @@ -448,10 +448,11 @@ static void pci_device_shutdown(struct device *dev)
> >
> > pm_runtime_resume(dev);
> >
> > - if (drv && drv->shutdown)
> > + if (drv && drv->shutdown) {
> > drv->shutdown(pci_dev);
> > - pci_msi_shutdown(pci_dev);
> > - pci_msix_shutdown(pci_dev);
> > + pci_msi_shutdown(pci_dev);
> > + pci_msix_shutdown(pci_dev);
> > + }
> >
> > #ifdef CONFIG_KEXEC
> > /*
> >
>
> The patch may be okay, but I think the bug here is also that virtio-pci
> is not defining a .shutdown callback. It should define one and call
> free_irq (for INTX) and pci_disable_msix.
It's not enough. The device has to know we disabled msix, otherwise it will
send us IRQ, which is wrong.
>
> How is this related to the virtio-scsi patch that you posted? Do you
> need both to fix the problem you reported?
>
This one should be enough. I was wrong in saying virtio-scsi hanging the
shutdown is because requests not being completed, it's more because of the
unexpected IRQ as explained in [1].
[1]: https://bugzilla.redhat.com/attachment.cgi?id=998391
Fam
next prev parent reply other threads:[~2015-03-12 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 5:21 [RFC PATCH] PCI: Disable MSI/MSI-X only if device is shutdown Fam Zheng
2015-03-12 16:21 ` Paolo Bonzini
2015-03-12 23:21 ` Fam Zheng
2015-03-12 23:21 ` Fam Zheng [this message]
2015-03-13 13:03 ` Paolo Bonzini
2015-03-13 13:03 ` Paolo Bonzini
2015-03-12 23:56 ` Bandan Das
2015-03-13 2:09 ` Fam Zheng
2015-03-13 3:09 ` Bandan Das
2015-03-13 3:17 ` Fam Zheng
2015-03-13 3:35 ` Bandan Das
2015-03-13 4:13 ` Alex Williamson
2015-03-13 4:53 ` Fam Zheng
2015-03-16 12:14 ` Michael S. Tsirkin
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=20150312232104.GA32054@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.