From: Betty Dall <betty.dall@hp.com>
To: Chen Gong <gong.chen@linux.intel.com>
Cc: rjw@sisk.pl, bhelgaas@google.com, ying.huang@intel.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 3/3] PCI/AER: Provide reset_link for firmware first root port
Date: Tue, 04 Jun 2013 15:38:51 -0600 [thread overview]
Message-ID: <1370381931.20051.101.camel@ejdallLaptop> (raw)
In-Reply-To: <20130604083644.GD20448@gchen.bj.intel.com>
On Tue, 2013-06-04 at 04:36 -0400, Chen Gong wrote:
> On Thu, May 30, 2013 at 08:39:29AM -0600, Betty Dall wrote:
> > Date: Thu, 30 May 2013 08:39:29 -0600
> > From: Betty Dall <betty.dall@hp.com>
> > To: rjw@sisk.pl, bhelgaas@google.com
> > Cc: ying.huang@intel.com, linux-acpi@vger.kernel.org,
> > linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, Betty Dall
> > <betty.dall@hp.com>
> > Subject: [PATCH v2 3/3] PCI/AER: Provide reset_link for firmware first root
> > port
> > X-Mailer: git-send-email 1.7.7.6
> >
> > The firmware first path does not install the aerdrv root port
> > service driver, so the firmware first root port does not have
> > a reset_link callback. When a firmware first root port does not have
> > a reset_link callback, use a new default reset_link similar to what
> > we already do for the default_downstream_reset_link(). The firmware
> > first default reset_link brings the root port out of SBR if firmware
> > left it in SBR.
> >
> > Changes since v1:
> > Removed incorrect setting of p2p_ctrl after the read.
> >
> > Signed-off-by: Betty Dall <betty.dall@hp.com>
> > ---
> >
> > drivers/pci/pcie/aer/aerdrv_core.c | 36 ++++++++++++++++++++++++++++++++++++
> > 1 files changed, 36 insertions(+), 0 deletions(-)
> >
> >
> > diff --git a/drivers/pci/pcie/aer/aerdrv_core.c b/drivers/pci/pcie/aer/aerdrv_core.c
> > index 8ec8b4f..72f76cd 100644
> > --- a/drivers/pci/pcie/aer/aerdrv_core.c
> > +++ b/drivers/pci/pcie/aer/aerdrv_core.c
> > @@ -413,6 +413,39 @@ static pci_ers_result_t default_downstream_reset_link(struct pci_dev *dev)
> > return PCI_ERS_RESULT_RECOVERED;
> > }
> >
> > +/**
> > + * default_ff_root_port_reset_link - default reset function for firmware
> > + * first Root Port
> > + * @dev: pointer to root port's pci_dev data structure
> > + *
> > + * Invoked when performing link reset at Root Port w/ no aer driver.
> > + * This happens through the firmware first path. Firmware may leave
> > + * the Root Port in SBR and it is the OS responsiblity to bring it out
> > + * of SBR.
> > + */
> > +static pci_ers_result_t default_ff_root_port_reset_link(struct pci_dev *dev)
> > +{
> > + u16 p2p_ctrl;
> > +
> > + /* Read Secondary Bus Reset */
> > + pci_read_config_word(dev, PCI_BRIDGE_CONTROL, &p2p_ctrl);
> > +
> > + /* De-assert Secondary Bus Reset, if it is set */
> > + if (p2p_ctrl & PCI_BRIDGE_CTL_BUS_RESET) {
> > + p2p_ctrl &= ~PCI_BRIDGE_CTL_BUS_RESET;
> > + pci_write_config_word(dev, PCI_BRIDGE_CONTROL, p2p_ctrl);
> > +
> > + /*
> > + * System software must wait for at least 100ms from the end
> > + * of a reset of one or more device before it is permitted
> > + * to issue Configuration Requests to those devices.
> > + */
> > + msleep(200);
> > + dev_dbg(&dev->dev, "Root Port link has been reset\n");
> > + }
> > + return PCI_ERS_RESULT_RECOVERED;
> > +}
>
> I don't think this function is OK.
> 1) You don't really reset the 2nd Bus but just checking its status.
> I think you should have following steps to reset 2nd Bus:
>
> a. Assert 2nd Bus Reset
> b. wait for some time until this message has been broadcasted well
> c. De-assert 2nd Bus Reset
> d. wait for Trst time
>
> IOW, since we have aer_do_secondary_bus_reset to perform secondary bus
> reset, why you repeat it again?
>
> 2) msleep(200) is too long for kernel. You'd better yield the CPU when
> sleep.
The firmware first path currently has no reset_link. I want to make a
minimal change since resetting the link could be considered firmware's
job in the firmware first path. This change is to just check if SBR is
set, and bring the link out of reset only if it is in SBR. This way, if
a another firmware first platform is already resetting the link, it
won't be done twice. I took the msleep and the code from
aer_do_sercondary_bus_reset() as you noticed.
-Betty
> > +
> > static int find_aer_service_iter(struct device *device, void *data)
> > {
> > struct pcie_port_service_driver *service_driver, **drv;
> > @@ -460,6 +493,9 @@ static pci_ers_result_t reset_link(struct pci_dev *dev)
> > status = driver->reset_link(udev);
> > } else if (pci_pcie_type(udev) == PCI_EXP_TYPE_DOWNSTREAM) {
> > status = default_downstream_reset_link(udev);
> > + } else if (pci_pcie_type(udev) == PCI_EXP_TYPE_ROOT_PORT &&
> > + pcie_aer_get_firmware_first(udev)) {
> > + status = default_ff_root_port_reset_link(udev);
> > } else {
> > dev_printk(KERN_DEBUG, &dev->dev,
> > "no link-reset support at upstream device %s\n",
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2013-06-04 21:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 14:39 [PATCH v2 0/3] PCI/ACPI: Fix firmware first error recovery with root port in reset Betty Dall
2013-05-30 14:39 ` [PATCH v2 1/3] PCI/AER: Fix incorrect return from aer_hest_parse() Betty Dall
2013-06-02 0:38 ` Bjorn Helgaas
2013-06-03 21:18 ` Betty Dall
2013-06-04 17:39 ` Bjorn Helgaas
2013-06-04 7:42 ` Chen Gong
2013-06-04 13:13 ` Bjorn Helgaas
2013-06-05 2:48 ` Chen Gong
2013-06-05 13:38 ` Bjorn Helgaas
2013-05-30 14:39 ` [PATCH v2 2/3] ACPI/APEI: Force fatal AER severity when bus has been reset Betty Dall
2013-06-04 7:53 ` Chen Gong
2013-06-04 16:20 ` Betty Dall
2013-06-04 17:54 ` Bjorn Helgaas
2013-06-05 1:56 ` Chen Gong
2013-05-30 14:39 ` [PATCH v2 3/3] PCI/AER: Provide reset_link for firmware first root port Betty Dall
2013-06-04 8:36 ` Chen Gong
2013-06-04 18:31 ` Bjorn Helgaas
2013-06-04 21:38 ` Betty Dall [this message]
2013-06-04 22:15 ` Bjorn Helgaas
2013-06-05 1:56 ` Chen Gong
2013-06-05 13:22 ` Betty Dall
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=1370381931.20051.101.camel@ejdallLaptop \
--to=betty.dall@hp.com \
--cc=bhelgaas@google.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=ying.huang@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).