From: Keith Busch <keith.busch@intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Sinan Kaya <okaya@kernel.org>, Thomas Tai <thomas.tai@oracle.com>,
poza@codeaurora.org
Subject: Re: [PATCH 13/16] PCI/pciehp: Implement error handling callbacks
Date: Tue, 4 Sep 2018 08:19:02 -0600 [thread overview]
Message-ID: <20180904141902.GH9677@localhost.localdomain> (raw)
In-Reply-To: <20180902103955.563lmxzzq52eo26q@wunner.de>
On Sun, Sep 02, 2018 at 12:39:55PM +0200, Lukas Wunner wrote:
> On Fri, Aug 31, 2018 at 03:26:36PM -0600, Keith Busch wrote:
> > + /*
> > + * Shutdown notification to ignore hotplug events during error
> > + * handling. We'll recheck the status when error handling completes.
> > + *
> > + * It is possible link event related to this error handling may have
> > + * triggered a the hotplug interrupt ahead of this notification, but we
> > + * can't do anything about that race.
> > + */
> > + pcie_shutdown_notification(ctrl);
>
> No, if you look at pciehp_remove() you'll notice that I call pci_hp_del()
> before pcie_shutdown_notification(). The IRQ thread is needed to respond
> to user requests to enable/disable the slot. If you just release the IRQ,
> the sysfs interface is still there but will no longer function while the
> reset is handled. Not good.
>
> I think what you want to do instead is "down_write(&ctrl->reset_lock)",
> see commit 5b3f7b7d062b ("PCI: pciehp: Avoid slot access during reset").
> And possibly mask PDCE/DLLSCE like pciehp_reset_slot() does.
>
>
> > +static void pciehp_slot_reset(struct pci_dev *dev)
> [...]
> > + /*
> > + * Cache presence detect change, but ignore other hotplug events that
> > + * may occur during error handling. Ports that implement only in-band
> > + * presence detection may inadvertently believe the device has changed,
> > + * so those devices will have to be re-enumerated.
> > + */
> > + pciehp_get_adapter_changed(ctrl->slot, &changed);
> > + pcie_clear_hotplug_events(ctrl);
> > + if (changed)
> > + pciehp_request(ctrl, PCI_EXP_SLTSTA_PDC);
> > + pcie_init_notification(ctrl);
> > +}
>
> Hm, can we be certain that error handling does not affect PDC?
No, I'm actually saying exactly the opposite in the code comments. The
error handling may affect PDC if the port doesn't have an out-of-band
presence detection capability.
> Because pciehp_reset_slot() does mask it and Sinan once said that in-band
> presence detect may cause presence to flap as well during reset:
> https://lkml.org/lkml/2018/7/3/693
Right, but how do you know which PDC is okay to ignore and which one
isn't? Hotplug events freqently trigger other error handling so we can't
just ignore hot plug during error handling. Link events should be safe
to ignore, though.
next prev parent reply other threads:[~2018-09-04 18:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 21:26 [PATCH 00/16] PCI, error handling and hot plug Keith Busch
2018-08-31 21:26 ` [PATCH 01/16] PCI: Simplify disconnected marking Keith Busch
2018-08-31 21:26 ` [PATCH 02/16] PCI: Fix pci_reset_bus Keith Busch
2018-08-31 21:52 ` Sinan Kaya
2018-08-31 22:08 ` Keith Busch
2018-08-31 21:26 ` [PATCH 03/16] PCI/AER: Remove dead code Keith Busch
2018-08-31 21:26 ` [PATCH 04/16] PCI/ERR: Use slot reset if available Keith Busch
2018-09-01 17:20 ` Lukas Wunner
2018-09-04 14:53 ` Keith Busch
2018-08-31 21:26 ` [PATCH 05/16] PCI/ERR: Handle fatal error recovery Keith Busch
2018-09-01 8:31 ` Christoph Hellwig
2018-09-05 5:56 ` poza
2018-08-31 21:26 ` [PATCH 06/16] PCI/ERR: Remove devices on recovery failure Keith Busch
2018-08-31 22:26 ` Sinan Kaya
2018-08-31 21:26 ` [PATCH 07/16] PCI/ERR: Always use the first downstream port Keith Busch
2018-08-31 21:26 ` [PATCH 08/16] PCI/ERR: Simplify broadcast callouts Keith Busch
2018-09-01 8:33 ` Christoph Hellwig
2018-08-31 21:26 ` [PATCH 09/16] PCI/ERR: Report current recovery status for udev Keith Busch
2018-09-01 8:36 ` Christoph Hellwig
2018-08-31 21:26 ` [PATCH 10/16] PCI/portdrv: Provide pci error callbacks Keith Busch
2018-09-02 10:16 ` Lukas Wunner
2018-09-04 21:38 ` Keith Busch
2018-08-31 21:26 ` [PATCH 11/16] PCI/portdrv: Restore pci state on slot reset Keith Busch
2018-09-02 9:34 ` Lukas Wunner
2018-09-04 14:36 ` Keith Busch
2018-08-31 21:26 ` [PATCH 12/16] PCI/pciehp: Fix powerfault detection order Keith Busch
2018-09-01 15:18 ` Lukas Wunner
2018-09-04 14:27 ` Keith Busch
2018-08-31 21:26 ` [PATCH 13/16] PCI/pciehp: Implement error handling callbacks Keith Busch
2018-09-02 10:39 ` Lukas Wunner
2018-09-04 14:19 ` Keith Busch [this message]
2018-08-31 21:26 ` [PATCH 14/16] pciehp: Ignore link events during DPC event Keith Busch
2018-08-31 22:18 ` Sinan Kaya
2018-08-31 22:33 ` Keith Busch
2018-08-31 22:55 ` Sinan Kaya
2018-08-31 22:59 ` Keith Busch
2018-08-31 23:07 ` Sinan Kaya
2018-09-02 14:27 ` Lukas Wunner
2018-09-04 14:16 ` Keith Busch
2018-09-04 14:40 ` Lukas Wunner
2018-09-04 15:31 ` Keith Busch
2018-08-31 21:26 ` [PATCH 15/16] PCI/DPC: Wait for reset complete Keith Busch
2018-08-31 22:15 ` Sinan Kaya
2018-08-31 21:26 ` [PATCH 16/16] PCI: Unify device inaccessible Keith Busch
2018-09-02 14:39 ` Lukas Wunner
2018-09-03 0:38 ` Benjamin Herrenschmidt
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=20180904141902.GH9677@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=okaya@kernel.org \
--cc=poza@codeaurora.org \
--cc=thomas.tai@oracle.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).