From: Alex Williamson <alex.williamson@redhat.com>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: bhelgaas@google.com, jbarnes@virtuousgeek.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Device specific reset function
Date: Mon, 12 Mar 2012 20:42:35 -0600 [thread overview]
Message-ID: <1331606555.22608.6.camel@ul30vt> (raw)
In-Reply-To: <4f5e2a73.YyO0Gu2m5JhSVsu6%tadeusz.struk@intel.com>
On Mon, 2012-03-12 at 16:55 +0000, Tadeusz Struk wrote:
> I have a use case where I need to cleanup resource allocated for Virtual
> Functions after a guest OS that used it crashed. This cleanup needs to
> be done before the VF is being FLRed. The only possible way to do this
> seems to be by using pci_dev_specific_reset() function.
> This patch adds specific reset function to the pci_driver struct.
>
> Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
> ---
> drivers/pci/quirks.c | 4 ++++
> include/linux/pci.h | 1 +
> 2 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index 6476547..13d224b 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -3081,8 +3081,12 @@ static const struct pci_dev_reset_methods pci_dev_reset_methods[] = {
>
> int pci_dev_specific_reset(struct pci_dev *dev, int probe)
> {
> + struct pci_driver *drv = dev->driver;
> const struct pci_dev_reset_methods *i;
>
> + if (drv && drv->reset)
> + return drv->reset(dev, probe);
> +
Isn't this exactly what the below code is for (pci_dev_reset_methods)?
In the case of KVM device assignment, the device should be reset via
this path if the guest crashes, but it may or may not be attached to
pci-stub at the time. I assume you're not adding a reset handler to
pci-stub, so we'll pass through here and use FLR, violating the premise
of the patch. Thanks,
Alex
> for (i = pci_dev_reset_methods; i->reset; i++) {
> if ((i->vendor == dev->vendor ||
> i->vendor == (u16)PCI_ANY_ID) &&
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index a16b1df..2ccd838 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -560,6 +560,7 @@ struct pci_driver {
> int (*resume_early) (struct pci_dev *dev);
> int (*resume) (struct pci_dev *dev); /* Device woken up */
> void (*shutdown) (struct pci_dev *dev);
> + int (*reset) (struct pci_dev *dev, int probe);
> struct pci_error_handlers *err_handler;
> struct device_driver driver;
> struct pci_dynids dynids;
next prev parent reply other threads:[~2012-03-13 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 16:55 [PATCH] PCI: Device specific reset function Tadeusz Struk
2012-03-13 2:42 ` Alex Williamson [this message]
2012-03-14 8:45 ` Tadeusz Struk
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=1331606555.22608.6.camel@ul30vt \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tadeusz.struk@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;
as well as URLs for NNTP newsgroup(s).