From: Govinda Tatti <Govinda.Tatti@Oracle.COM>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: jgross@suse.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, JBeulich@suse.com,
bhelgaas@google.com, xen-devel@lists.xenproject.org,
boris.ostrovsky@Oracle.COM, roger.pau@citrix.com
Subject: Re: [Xen-devel] [PATCH V3 1/2] Drivers/PCI: Export pcie_has_flr() interface
Date: Wed, 13 Dec 2017 14:46:57 -0600 [thread overview]
Message-ID: <49956aaf-5fd5-939d-5fc7-231ffdb98b70@Oracle.COM> (raw)
In-Reply-To: <20171212005919.GB30595@bhelgaas-glaptop.roam.corp.google.com>
>>>> -static bool pcie_has_flr(struct pci_dev *dev)
>>>> +bool pcie_has_flr(struct pci_dev *dev)
>>>> {
>>>> u32 cap;
>>>> @@ -3882,6 +3882,7 @@ static bool pcie_has_flr(struct pci_dev *dev)
>>>> pcie_capability_read_dword(dev, PCI_EXP_DEVCAP, &cap);
>>>> return cap & PCI_EXP_DEVCAP_FLR;
>>>> }
>>>> +EXPORT_SYMBOL_GPL(pcie_has_flr);
>>> I'd rather change pcie_flr() so you could *always* call it, and it
>>> would return 0, -ENOTTY, or whatever, based on whether FLR is
>>> supported. Is that feasible?
>> Sure, I will add pcie_has_flr() logic inside pcie_flr() and return
>> appropriate
>> values as suggested by you. Do we still want to retain pcie_has_flr() and
>> its usage inside pci.c?.Otherwise, I will remove it and do required cleanup.
> If you can restructure the code and remove pcie_has_flr() while
> retaining the existing behavior of its callers, that would be great.
I checked the current usage of pcie_has_flr() and pcie_flr(). I have a
couple
of questions or need some clarification.
1. pcie_has_flr() usage inside pci_probe_reset_function().
This function is only calling pcie_has_flr() but not pcie_flr().
Rest of the code is trying to do specific type of reset except
pcie_flr().
rc = pci_dev_specific_reset(dev, 1);
if (rc != -ENOTTY)
return rc;
if (pcie_has_flr(dev))
return 0;
rc = pci_af_flr(dev, 1);
if (rc != -ENOTTY)
return rc;
In other-words, I can remove usage of pcie_has_flr() in all other places
in pci.c except in above function.
2. W.r.t pcie_flr(), I am planning to return error code. Currently, the
following
file/modules are calling this function. My plan is to add a check
for return
code and print a WANRING message if return code is NON-ZERO. I hope
this is
sufficient for this patch.
drivers/crypto/qat/qat_common/adf_aer.c
drivers/infiniband/hw/hfi1/chip.c (2 places)
drivers/net/ethernet/cavium/liquidio/lio_vf_main.c
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c (2 places)
drivers/pci/quirks.c (2 places)
Cheers
GOVINDA
next prev parent reply other threads:[~2017-12-13 20:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 22:21 [PATCH V3 0/2] Xen/PCIback: PCI reset using 'reset' SysFS attribute Govinda Tatti
2017-12-07 22:21 ` [PATCH V3 1/2] Drivers/PCI: Export pcie_has_flr() interface Govinda Tatti
2017-12-08 20:24 ` Bjorn Helgaas
2017-12-12 0:29 ` Govinda Tatti
2017-12-12 0:59 ` Bjorn Helgaas
2017-12-13 20:46 ` Govinda Tatti [this message]
2017-12-13 21:24 ` [Xen-devel] " Bjorn Helgaas
2017-12-14 12:52 ` Christoph Hellwig
2017-12-15 0:24 ` Bjorn Helgaas
2017-12-15 15:48 ` Govinda Tatti
2017-12-15 18:18 ` Bjorn Helgaas
2017-12-15 20:01 ` Govinda Tatti
2017-12-18 3:09 ` Alexey Kardashevskiy
2017-12-18 12:26 ` Christoph Hellwig
2017-12-18 17:22 ` Govinda Tatti
2018-09-09 18:59 ` Pasi Kärkkäinen
2018-09-10 2:33 ` Sinan Kaya
2018-09-10 9:52 ` Pasi Kärkkäinen
2018-09-10 17:04 ` Sinan Kaya
2017-12-12 15:07 ` Christoph Hellwig
2017-12-07 22:21 ` [PATCH V3 2/2] Xen/PCIback: Implement PCI flr/slot/bus reset with 'reset' SysFS attribute Govinda Tatti
2017-12-08 9:34 ` Jan Beulich
2017-12-12 15:01 ` Govinda Tatti
[not found] ` <8a3bc517-1255-4547-d244-5c400e44cc77@Oracle.COM>
2017-12-12 15:01 ` Jan Beulich
2017-12-12 15:14 ` [Xen-devel] " Govinda Tatti
2017-12-15 19:52 ` Govinda Tatti
2017-12-18 7:36 ` Jan Beulich
2017-12-18 17:32 ` Boris Ostrovsky
2018-09-16 11:43 ` [Xen-devel] " Pasi Kärkkäinen
2018-09-17 18:06 ` Boris Ostrovsky
2018-09-18 7:15 ` Pasi Kärkkäinen
2018-09-18 9:32 ` George Dunlap
2018-09-18 9:32 ` George Dunlap
2018-09-18 18:09 ` Boris Ostrovsky
2018-09-19 9:05 ` Roger Pau Monné
2018-10-03 15:51 ` Pasi Kärkkäinen
2018-10-08 14:32 ` Boris Ostrovsky
2019-08-26 21:05 ` Pasi Kärkkäinen
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=49956aaf-5fd5-939d-5fc7-231ffdb98b70@Oracle.COM \
--to=govinda.tatti@oracle.com \
--cc=JBeulich@suse.com \
--cc=bhelgaas@google.com \
--cc=boris.ostrovsky@Oracle.COM \
--cc=helgaas@kernel.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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).