From: Alex Williamson <alex.williamson@redhat.com>
To: Sinan Kaya <okaya@kernel.org>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Peter Xu <peterx@redhat.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Eric Auger <eric.auger@redhat.com>
Subject: Re: [PATCH v4 4/6] PCI: Expose reset type to users of pci_try_reset_function()
Date: Wed, 19 Sep 2018 13:00:38 -0600 [thread overview]
Message-ID: <20180919130038.0d5a152b@t450s.home> (raw)
In-Reply-To: <20180919163037.13497-5-okaya@kernel.org>
On Wed, 19 Sep 2018 16:30:35 +0000
Sinan Kaya <okaya@kernel.org> wrote:
> Looking to have more control between the users of the API vs. what the API
> can do internally. The new reset_type tells the PCI core about the bounds
> of the request.
>
> Signed-off-by: Sinan Kaya <okaya@kernel.org>
> ---
> drivers/pci/pci.c | 4 ++--
> drivers/vfio/pci/vfio_pci.c | 7 ++++---
> drivers/vfio/pci/vfio_pci_config.c | 4 ++--
> include/linux/pci.h | 2 +-
> 4 files changed, 9 insertions(+), 8 deletions(-)
Acked-by: Alex Williamson <alex.williamson@redhat.com>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 63b5930d8fb1..4edf70a4d528 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -4852,7 +4852,7 @@ EXPORT_SYMBOL_GPL(pci_reset_function_locked);
> *
> * Same as above, except return -EAGAIN if unable to lock device.
> */
> -int pci_try_reset_function(struct pci_dev *dev)
> +int pci_try_reset_function(struct pci_dev *dev, u32 reset_type)
> {
> int rc;
>
> @@ -4863,7 +4863,7 @@ int pci_try_reset_function(struct pci_dev *dev)
> return -EAGAIN;
>
> pci_dev_save_and_disable(dev);
> - rc = __pci_reset_function_locked(dev, PCI_RESET_ANY);
> + rc = __pci_reset_function_locked(dev, reset_type);
> pci_dev_restore(dev);
> pci_dev_unlock(dev);
>
> diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
> index cddb453a1ba5..fe7ada997c51 100644
> --- a/drivers/vfio/pci/vfio_pci.c
> +++ b/drivers/vfio/pci/vfio_pci.c
> @@ -228,7 +228,7 @@ static int vfio_pci_enable(struct vfio_pci_device *vdev)
> return ret;
>
> /* If reset fails because of the device lock, fail this path entirely */
> - ret = pci_try_reset_function(pdev);
> + ret = pci_try_reset_function(pdev, PCI_RESET_ANY);
> if (ret == -EAGAIN) {
> pci_disable_device(pdev);
> return ret;
> @@ -376,7 +376,7 @@ static void vfio_pci_disable(struct vfio_pci_device *vdev)
> * Try to reset the device. The success of this is dependent on
> * being able to lock the device, which is not always possible.
> */
> - if (vdev->reset_works && !pci_try_reset_function(pdev))
> + if (vdev->reset_works && !pci_try_reset_function(pdev, PCI_RESET_ANY))
> vdev->needs_reset = false;
>
> pci_restore_state(pdev);
> @@ -844,7 +844,8 @@ static long vfio_pci_ioctl(void *device_data,
>
> } else if (cmd == VFIO_DEVICE_RESET) {
> return vdev->reset_works ?
> - pci_try_reset_function(vdev->pdev) : -EINVAL;
> + pci_try_reset_function(vdev->pdev, PCI_RESET_ANY) :
> + -EINVAL;
>
> } else if (cmd == VFIO_DEVICE_GET_PCI_HOT_RESET_INFO) {
> struct vfio_pci_hot_reset_info hdr;
> diff --git a/drivers/vfio/pci/vfio_pci_config.c b/drivers/vfio/pci/vfio_pci_config.c
> index 115a36f6f403..0d66bac66211 100644
> --- a/drivers/vfio/pci/vfio_pci_config.c
> +++ b/drivers/vfio/pci/vfio_pci_config.c
> @@ -831,7 +831,7 @@ static int vfio_exp_config_write(struct vfio_pci_device *vdev, int pos,
> &cap);
>
> if (!ret && (cap & PCI_EXP_DEVCAP_FLR))
> - pci_try_reset_function(vdev->pdev);
> + pci_try_reset_function(vdev->pdev, PCI_RESET_ANY);
> }
>
> /*
> @@ -910,7 +910,7 @@ static int vfio_af_config_write(struct vfio_pci_device *vdev, int pos,
> &cap);
>
> if (!ret && (cap & PCI_AF_CAP_FLR) && (cap & PCI_AF_CAP_TP))
> - pci_try_reset_function(vdev->pdev);
> + pci_try_reset_function(vdev->pdev, PCI_RESET_ANY);
> }
>
> return count;
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 09aa99dd1c1b..4fdddcb85066 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -1125,7 +1125,7 @@ int pcie_flr(struct pci_dev *dev);
> int __pci_reset_function_locked(struct pci_dev *dev, u32 reset_type);
> int pci_reset_function(struct pci_dev *dev, u32 reset_type);
> int pci_reset_function_locked(struct pci_dev *dev, u32 reset_type);
> -int pci_try_reset_function(struct pci_dev *dev);
> +int pci_try_reset_function(struct pci_dev *dev, u32 reset_type);
> int pci_probe_reset_slot(struct pci_slot *slot);
> int pci_probe_reset_bus(struct pci_bus *bus);
> int pci_reset_bus(struct pci_dev *dev);
next prev parent reply other threads:[~2018-09-20 0:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 16:30 [PATCH v4 0/6] PCI: Add reset type parameter to PCI reset functions Sinan Kaya
2018-09-19 16:30 ` [PATCH v4 1/6] PCI: Expose reset_type to users of __pci_reset_function_locked() Sinan Kaya
2018-09-25 20:45 ` Bjorn Helgaas
2018-09-25 21:07 ` Sinan Kaya
2018-09-25 21:58 ` Bjorn Helgaas
2018-09-19 16:30 ` [PATCH v4 2/6] PCI: Expose reset_type to users of pci_reset_function() Sinan Kaya
2018-09-25 20:46 ` Bjorn Helgaas
2018-09-25 20:52 ` Sinan Kaya
2018-09-25 21:59 ` Bjorn Helgaas
2018-09-19 16:30 ` [PATCH v4 3/6] PCI: Expose reset_type to users of pci_reset_function_locked() Sinan Kaya
2018-09-19 16:30 ` [PATCH v4 4/6] PCI: Expose reset type to users of pci_try_reset_function() Sinan Kaya
2018-09-19 19:00 ` Alex Williamson [this message]
2018-09-19 16:30 ` [PATCH v4 5/6] PCI: Expose reset type to users of pci_probe_reset_function() Sinan Kaya
2018-09-19 16:30 ` [PATCH v4 6/6] PCI: Expose reset type to users of pci_reset_bus() Sinan Kaya
2018-09-19 19:00 ` Alex Williamson
2018-09-25 20:54 ` Bjorn Helgaas
2018-09-25 21:15 ` Sinan Kaya
2018-09-25 21:56 ` Bjorn Helgaas
2018-09-25 22:18 ` Sinan Kaya
2018-09-19 19:02 ` [PATCH v4 0/6] PCI: Add reset type parameter to PCI reset functions Alex Williamson
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=20180919130038.0d5a152b@t450s.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=bhelgaas@google.com \
--cc=eric.auger@redhat.com \
--cc=gustavo@embeddedor.com \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@kernel.org \
--cc=peterx@redhat.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).