From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Fam Zheng <famz@redhat.com>,
Yinghai Lu <yhlu.kernel.send@gmail.com>,
Yijing Wang <wangyijing@huawei.com>,
Ulrich Obergfell <uobergfe@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH v6 1/2] PCI/MSI: Don't disable MSI/MSI-X at shutdown
Date: Thu, 14 May 2015 08:06:00 +0200 [thread overview]
Message-ID: <20150514075957-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150513081101-mutt-send-email-mst@redhat.com>
On Wed, May 13, 2015 at 08:41:55AM +0200, Michael S. Tsirkin wrote:
> > This also sounds like a case for implementing a shutdown callback and
> > disabling things properly. A properly shutdown driver should have
> > already disabled MSI's. A driver is responsible for enabling MSIs so it
> > should be responsible for disabling it. The core disabling MSIs is
> > mostly to catch the handful of lazy drivers that forget.
>
>
> Okay! And I am saying that if the driver did forget,
> we are better off not disabling it - leave it enabled
> until kexec starts and disables it.
>
>
> > The bottom line is that there are a few things that are standard
> > behavior that we can do in the generic code, but at the end of the day
> > it is the responsibility of the driver to shut things down and whatever
> > driver you are dealing with clearly has a bunch of bugs and you aren't
> > fixing it.
>
> So please let us get on with fixing it in driver and stop
> playing with device in core.
Eric, does this argument make sense? Drivers should do the right thing
in their shutdown callback, let's not try to work around their bugs in
core.
--
MST
next prev parent reply other threads:[~2015-05-14 6:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 13:03 [PATCH v6 0/2] pci: drop msi disable on shutdown Michael S. Tsirkin
2015-05-12 13:03 ` [PATCH v6 1/2] PCI/MSI: Don't disable MSI/MSI-X at shutdown Michael S. Tsirkin
2015-05-12 19:22 ` Eric W. Biederman
2015-05-13 6:41 ` Michael S. Tsirkin
2015-05-14 6:06 ` Michael S. Tsirkin [this message]
2015-05-14 7:58 ` Eric W. Biederman
2015-05-14 9:53 ` Michael S. Tsirkin
2015-05-28 16:36 ` Michael S. Tsirkin
2015-06-03 18:37 ` Michael S. Tsirkin
2015-05-19 14:58 ` Bjorn Helgaas
2015-05-21 6:21 ` Fam Zheng
2015-05-12 13:03 ` [PATCH v6 2/2] PCI/MSI: Make pci_msi_shutdown(), pci_msix_shutdown() static 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=20150514075957-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=bhelgaas@google.com \
--cc=ebiederm@xmission.com \
--cc=famz@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=uobergfe@redhat.com \
--cc=wangyijing@huawei.com \
--cc=yhlu.kernel.send@gmail.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).