From: Bjorn Helgaas <bhelgaas@google.com>
To: "Michael S. Tsirkin" <mst@kernel.org>
Cc: Yijing Wang <wangyijing@huawei.com>,
linux-pci@vger.kernel.org, Fam Zheng <famz@redhat.com>,
Yinghai Lu <yinghai@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH v6 00/10] PCI: Fix unhandled interrupt on shutdown
Date: Wed, 6 May 2015 16:03:27 -0500 [thread overview]
Message-ID: <20150506210327.GG24643@google.com> (raw)
In-Reply-To: <20150426084739-mutt-send-email-mst@kernel.org>
On Sun, Apr 26, 2015 at 08:50:06AM +0200, Michael S. Tsirkin wrote:
> On Fri, Apr 10, 2015 at 05:54:19PM -0500, Bjorn Helgaas wrote:
> > Hi Michael,
> >
> > I put your patches on my pci/msi branch and I hope to merge them for v4.1.
> > I didn't apply the acks from Fam and Eric because I made changes to those
> > patches that weren't completely trivial. I think the end result is
> > equivalent, though. The diff attached to this cover letter is the
> > difference between your v5 series and this v6 series.
> >
> > As far as I'm concerned, this is ready to go except that I would like a
> > little more info about the virtio kernel hang to include in the changelog
> > for "PCI/MSI: Don't disable MSI/MSI-X at shutdown".
>
>
> Hi Bjorn,
> do you have eveything you need to merge this?
No. I made the minor changelog edits you suggested and the result is on
my pci/msi-v7 branch. But I still have these open issues:
- The last thing I heard from Eric was that "not disabling MSI/MSI-X at
shutdown is the wrong fix, and someone needs to fix a buggy driver."
I want to hear Eric say "OK, we need to leave MSI/MSI-X enabled at
shutdown for this case."
- One changelog says "Stop disabling MSIs at shutdown to avoid
conflicting with drivers." But I don't know what the conflict is.
- The bugzilla has no dmesg log or detailed analysis. Fam said the
scenario I came up with
(http://lkml.kernel.org/r/20150416194245.GB20701@google.com)
was fairly close, but it took me a lot of work to derive that. Fixing
any errors in it and putting it in the bugzilla would be a big step.
The bugzilla should have the raw data and the analysis, so someone else
can validate the analysis and conclude that this patch is a reasonable
fix for it. That's currently impossible because the bugzilla really
only contains the fix as a fait accompli.
Bjorn
next prev parent reply other threads:[~2015-05-06 21:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 22:54 [PATCH v6 00/10] PCI: Fix unhandled interrupt on shutdown Bjorn Helgaas
2015-04-10 22:54 ` [PATCH v6 01/10] PCI/MSI: Rename msi_set_enable(), msix_clear_and_set_ctrl() Bjorn Helgaas
2015-04-11 7:30 ` Greg KH
2015-04-11 16:01 ` Bjorn Helgaas
2015-04-10 22:54 ` [PATCH v6 02/10] PCI/MSI: Export pci_msi_set_enable(), pci_msix_clear_and_set_ctrl() Bjorn Helgaas
2015-04-10 22:54 ` [PATCH v6 03/10] PCI/MSI: Disable MSI at enumeration even if kernel doesn't support MSI Bjorn Helgaas
2015-04-10 22:54 ` [PATCH v6 04/10] PCI/MSI: Don't disable MSI/MSI-X at shutdown Bjorn Helgaas
2015-04-13 9:37 ` Fam Zheng
2015-04-13 15:41 ` Bjorn Helgaas
2015-04-13 16:45 ` Eric W. Biederman
2015-04-14 9:44 ` Michael S. Tsirkin
2015-04-16 19:42 ` Bjorn Helgaas
2015-04-17 1:05 ` Fam Zheng
2015-04-14 9:47 ` Michael S. Tsirkin
2015-04-14 10:45 ` Fam Zheng
2015-04-14 10:49 ` Michael S. Tsirkin
2015-04-16 7:30 ` Michael S. Tsirkin
2015-04-10 22:54 ` [PATCH v6 05/10] PCI/MSI: Make pci_msi_shutdown(), pci_msix_shutdown() static Bjorn Helgaas
2015-04-10 22:55 ` [PATCH v6 06/10] virtio_pci: drop pci_msi_off() call during probe Bjorn Helgaas
2015-04-10 22:55 ` [PATCH v6 07/10] ntb: Drop " Bjorn Helgaas
2015-04-10 22:55 ` [PATCH v6 08/10] mic: " Bjorn Helgaas
2015-04-10 22:55 ` [PATCH v6 09/10] PCI/MSI: Drop pci_msi_off() calls from quirks Bjorn Helgaas
2015-04-10 22:55 ` [PATCH v6 10/10] PCI/MSI: Remove unused pci_msi_off() Bjorn Helgaas
2015-04-26 6:50 ` [PATCH v6 00/10] PCI: Fix unhandled interrupt on shutdown Michael S. Tsirkin
2015-05-06 21:03 ` Bjorn Helgaas [this message]
2015-05-07 0:53 ` Eric W. Biederman
2015-05-07 15:04 ` Bjorn Helgaas
2015-05-10 11:05 ` Michael S. Tsirkin
2015-05-10 11:09 ` Michael S. Tsirkin
2015-05-10 11:42 ` 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=20150506210327.GG24643@google.com \
--to=bhelgaas@google.com \
--cc=ebiederm@xmission.com \
--cc=famz@redhat.com \
--cc=linux-pci@vger.kernel.org \
--cc=mst@kernel.org \
--cc=wangyijing@huawei.com \
--cc=yinghai@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).