On Thu, 1 May 2014, Bjorn Helgaas wrote:
On Thu, May 1, 2014 at 1:57 PM, Keith Busch <keith.busch@xxxxxxxxx> wrote:
On Wed, 30 Apr 2014, Bjorn Helgaas wrote:
On Tue, Apr 08, 2014 at 05:42:20PM -0600, Keith Busch wrote:
You put the notify in these functions:
pci_reset_function()
pci_try_reset_function()
but what about these:
pci_reset_slot()
pci_try_reset_slot()
pci_reset_bus()
pci_try_reset_bus()
Good point. These all call pci_dev_save_and_disable at the start and
pci_dev_restore after, so I think just adding the reset prepare/complete
to those functions should cover all scenarios. Does this sound ok?
Sound OK to me, as long as the save/restore functions aren't used elsewhere.
Yep, there is currently 1:1 symmetry for these in all cases. I'll make
a note for any future use that the calling disabling/restore should
maintain this property.
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
