From: Bjorn Helgaas <bhelgaas@google.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-pci@vger.kernel.org, Fam Zheng <famz@redhat.com>,
Yinghai Lu <yhlu.kernel.send@gmail.com>,
Ulrich Obergfell <uobergfe@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH v2 1/4] pci: disable msi/msix at probe time
Date: Mon, 23 Mar 2015 13:50:06 -0500 [thread overview]
Message-ID: <20150323185006.GT26935@google.com> (raw)
In-Reply-To: <1426786724-22241-2-git-send-email-mst@redhat.com>
Hi Michael,
On Thu, Mar 19, 2015 at 07:57:52PM +0100, Michael S. Tsirkin wrote:
> commit d52877c7b1afb8c37ebe17e2005040b79cb618b0
> pci/irq: let pci_device_shutdown to call pci_msi_shutdown v2
>
> attempted to address the problem of kexec getting
> started after linux enabled msi/msix for a device,
> and drivers being confused by msi being enabled,
> by disabling msi at shutdown.
>
> But arguably, it's better to disable msi/msix when kexec
> starts - for example, kexec might run after a crash (kdump)
> and shutdown callbacks are not always invoked in that case.
>
> Cc: Yinghai Lu <yhlu.kernel.send@gmail.com>
> Cc: Ulrich Obergfell <uobergfe@redhat.com>
> Cc: Fam Zheng <famz@redhat.com>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> drivers/pci/pci-driver.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> index 3cb2210..2ebd2a8 100644
> --- a/drivers/pci/pci-driver.c
> +++ b/drivers/pci/pci-driver.c
> @@ -305,6 +305,12 @@ static long local_pci_probe(void *_ddi)
> */
> pm_runtime_get_sync(dev);
> pci_dev->driver = pci_drv;
> + /*
> + * When using kexec, msi might be left enabled by the previous kernel,
> + * this breaks things as some drivers assume msi/msi-x is off at boot.
> + * Fix this by forcing msi off at startup.
> + */
> + pci_msi_off(pci_dev);
I think this makes sense, but I have a few questions. This is a device
initialization thing, so it seems like a better fit for the enumeration
path, e.g,. pci_msi_init_pci_dev(), than for the driver binding path.
But when CONFIG_PCI_MSI=y, pci_msi_init_pci_dev() already does basically
the same thing, so we shouldn't need this change unless CONFIG_PCI_MSI is
not set in the kdump kernel.
If this is a problem just with kexeced kernels that don't have
CONFIG_PCI_MSI=y, I think I would prefer to fix this by moving
pci_msi_init_pci_dev() outside the #ifdef so it works regardless of
CONFIG_PCI_MSI. That would also be nice because we could clean up the
duplication between pci_msi_off() and pci_msi_init_pci_dev(). It would
also make the starting machine state less dependent on the new kernel,
which seems like a good thing.
Are there any bugzillas we could reference here?
> rc = pci_drv->probe(pci_dev, ddi->id);
> if (!rc)
> return rc;
> --
> MST
>
next prev parent reply other threads:[~2015-03-23 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 18:57 [PATCH v2 0/4] pci: fix unhandled interrupt on shutdown Michael S. Tsirkin
2015-03-19 18:57 ` [PATCH v2 1/4] pci: disable msi/msix at probe time Michael S. Tsirkin
2015-03-23 18:50 ` Bjorn Helgaas [this message]
2015-03-23 19:22 ` Michael S. Tsirkin
2015-03-23 20:45 ` Bjorn Helgaas
2015-03-23 20:52 ` Michael S. Tsirkin
2015-03-19 18:58 ` [PATCH v2 2/4] pci: don't disable msi/msix at shutdown Michael S. Tsirkin
2015-03-19 18:58 ` [PATCH v2 3/4] pci: make msi/msix shutdown functions static Michael S. Tsirkin
2015-03-19 18:58 ` [PATCH v2 4/4] virtio_pci: drop msi_off on probe Michael S. Tsirkin
2015-03-19 18:58 ` Michael S. Tsirkin
2015-03-23 4:54 ` [PATCH v2 0/4] pci: fix unhandled interrupt on shutdown Fam Zheng
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=20150323185006.GT26935@google.com \
--to=bhelgaas@google.com \
--cc=famz@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=stable@vger.kernel.org \
--cc=uobergfe@redhat.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 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.