2018-01-27 03:22:04 +07:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0+ */
|
2005-04-17 05:20:36 +07:00
|
|
|
/*
|
|
|
|
|
* PCI HotPlug Core Functions
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 1995,2001 Compaq Computer Corporation
|
|
|
|
|
* Copyright (C) 2001 Greg Kroah-Hartman (greg@kroah.com)
|
|
|
|
|
* Copyright (C) 2001 IBM Corp.
|
|
|
|
|
*
|
|
|
|
|
* All rights reserved.
|
|
|
|
|
*
|
2006-09-30 00:30:27 +07:00
|
|
|
* Send feedback to <kristen.c.accardi@intel.com>
|
2005-04-17 05:20:36 +07:00
|
|
|
*
|
|
|
|
|
*/
|
|
|
|
|
#ifndef _PCI_HOTPLUG_H
|
|
|
|
|
#define _PCI_HOTPLUG_H
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* struct hotplug_slot_ops -the callbacks that the hotplug pci core can use
|
|
|
|
|
* @enable_slot: Called when the user wants to enable a specific pci slot
|
|
|
|
|
* @disable_slot: Called when the user wants to disable a specific pci slot
|
|
|
|
|
* @set_attention_status: Called to set the specific slot's attention LED to
|
|
|
|
|
* the specified value
|
|
|
|
|
* @hardware_test: Called to run a specified hardware test on the specified
|
|
|
|
|
* slot.
|
|
|
|
|
* @get_power_status: Called to get the current power status of a slot.
|
|
|
|
|
* @get_attention_status: Called to get the current attention status of a slot.
|
|
|
|
|
* @get_latch_status: Called to get the current latch status of a slot.
|
|
|
|
|
* @get_adapter_status: Called to get see if an adapter is present in the slot or not.
|
2013-08-09 03:09:31 +07:00
|
|
|
* @reset_slot: Optional interface to allow override of a bus reset for the
|
|
|
|
|
* slot for cases where a secondary bus reset can result in spurious
|
|
|
|
|
* hotplug events or where a slot can be reset independent of the bus.
|
2005-04-17 05:20:36 +07:00
|
|
|
*
|
|
|
|
|
* The table of function pointers that is passed to the hotplug pci core by a
|
|
|
|
|
* hotplug pci driver. These functions are called by the hotplug pci core when
|
|
|
|
|
* the user wants to do something to a specific slot (query it for information,
|
|
|
|
|
* set an LED, enable / disable power, etc.)
|
|
|
|
|
*/
|
|
|
|
|
struct hotplug_slot_ops {
|
|
|
|
|
int (*enable_slot) (struct hotplug_slot *slot);
|
|
|
|
|
int (*disable_slot) (struct hotplug_slot *slot);
|
|
|
|
|
int (*set_attention_status) (struct hotplug_slot *slot, u8 value);
|
|
|
|
|
int (*hardware_test) (struct hotplug_slot *slot, u32 value);
|
|
|
|
|
int (*get_power_status) (struct hotplug_slot *slot, u8 *value);
|
|
|
|
|
int (*get_attention_status) (struct hotplug_slot *slot, u8 *value);
|
|
|
|
|
int (*get_latch_status) (struct hotplug_slot *slot, u8 *value);
|
|
|
|
|
int (*get_adapter_status) (struct hotplug_slot *slot, u8 *value);
|
2013-08-09 03:09:31 +07:00
|
|
|
int (*reset_slot) (struct hotplug_slot *slot, int probe);
|
2005-04-17 05:20:36 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* struct hotplug_slot - used to register a physical slot with the hotplug pci core
|
|
|
|
|
* @ops: pointer to the &struct hotplug_slot_ops to be used for this slot
|
2018-09-08 14:59:01 +07:00
|
|
|
* @owner: The module owner of this structure
|
|
|
|
|
* @mod_name: The module name (KBUILD_MODNAME) of this structure
|
2005-04-17 05:20:36 +07:00
|
|
|
*/
|
|
|
|
|
struct hotplug_slot {
|
2018-09-08 14:59:01 +07:00
|
|
|
const struct hotplug_slot_ops *ops;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
|
/* Variables below this are for use only by the hotplug pci core. */
|
|
|
|
|
struct list_head slot_list;
|
2008-06-11 04:28:50 +07:00
|
|
|
struct pci_slot *pci_slot;
|
2018-09-08 14:59:01 +07:00
|
|
|
struct module *owner;
|
|
|
|
|
const char *mod_name;
|
2005-04-17 05:20:36 +07:00
|
|
|
};
|
|
|
|
|
|
2008-10-21 06:41:07 +07:00
|
|
|
static inline const char *hotplug_slot_name(const struct hotplug_slot *slot)
|
|
|
|
|
{
|
|
|
|
|
return pci_slot_name(slot->pci_slot);
|
|
|
|
|
}
|
|
|
|
|
|
2013-04-13 01:02:59 +07:00
|
|
|
int __pci_hp_register(struct hotplug_slot *slot, struct pci_bus *pbus, int nr,
|
|
|
|
|
const char *name, struct module *owner,
|
|
|
|
|
const char *mod_name);
|
PCI: hotplug: Demidlayer registration with the core
When a hotplug driver calls pci_hp_register(), all steps necessary for
registration are carried out in one go, including creation of a kobject
and addition to sysfs. That's a problem for pciehp once it's converted
to enable/disable the slot exclusively from the IRQ thread: The thread
needs to be spawned after creation of the kobject (because it uses the
kobject's name), but before addition to sysfs (because it will handle
enable/disable requests submitted via sysfs).
pci_hp_deregister() does offer a ->release callback that's invoked
after deletion from sysfs and before destruction of the kobject. But
because pci_hp_register() doesn't offer a counterpart, hotplug drivers'
->probe and ->remove code becomes asymmetric, which is error prone
as recently discovered use-after-free bugs in pciehp's ->remove hook
have shown.
In a sense, this appears to be a case of the midlayer antipattern:
"The core thesis of the "midlayer mistake" is that midlayers are
bad and should not exist. That common functionality which it is
so tempting to put in a midlayer should instead be provided as
library routines which can [be] used, augmented, or ignored by
each bottom level driver independently. Thus every subsystem
that supports multiple implementations (or drivers) should
provide a very thin top layer which calls directly into the
bottom layer drivers, and a rich library of support code that
eases the implementation of those drivers. This library is
available to, but not forced upon, those drivers."
-- Neil Brown (2009), https://lwn.net/Articles/336262/
The presence of midlayer traits in the PCI hotplug core might be ascribed
to its age: When it was introduced in February 2002, the blessings of a
library approach might not have been well known:
https://git.kernel.org/tglx/history/c/a8a2069f432c
For comparison, the driver core does offer split functions for creating
a kobject (device_initialize()) and addition to sysfs (device_add()) as
an alternative to carrying out everything at once (device_register()).
This was introduced in October 2002:
https://git.kernel.org/tglx/history/c/8b290eb19962
The odd ->release callback in the PCI hotplug core was added in 2003:
https://git.kernel.org/tglx/history/c/69f8d663b595
Clearly, a library approach would not force every hotplug driver to
implement a ->release callback, but rather allow the driver to remove
the sysfs files, release its data structures and finally destroy the
kobject. Alternatively, a driver may choose to remove everything with
pci_hp_deregister(), then release its data structures.
To this end, offer drivers pci_hp_initialize() and pci_hp_add() as a
split-up version of pci_hp_register(). Likewise, offer pci_hp_del()
and pci_hp_destroy() as a split-up version of pci_hp_deregister().
Eliminate the ->release callback and move its code into each driver's
teardown routine.
Declare pci_hp_deregister() void, in keeping with the usual kernel
pattern that enablement can fail, but disablement cannot. It only
returned an error if the caller passed in a NULL pointer or a slot which
has never or is no longer registered or is sharing its name with another
slot. Those would be bugs, so WARN about them. Few hotplug drivers
actually checked the return value and those that did only printed a
useless error message to dmesg. Remove that.
For most drivers the conversion was straightforward since it doesn't
matter whether the code in the ->release callback is executed before or
after destruction of the kobject. But in the case of ibmphp, it was
unclear to me whether setting slot_cur->ctrl and slot_cur->bus_on to
NULL needs to happen before the kobject is destroyed, so I erred on
the side of caution and ensured that the order stays the same. Another
nontrivial case is pnv_php, I've found the list and kref logic difficult
to understand, however my impression was that it is safe to delete the
list element and drop the references until after the kobject is
destroyed.
Signed-off-by: Lukas Wunner <lukas@wunner.de>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Acked-by: Andy Shevchenko <andy.shevchenko@gmail.com> # drivers/platform/x86
Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>
Cc: Scott Murray <scott@spiteful.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: Sebastian Ott <sebott@linux.vnet.ibm.com>
Cc: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Cc: Corentin Chary <corentin.chary@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>
Cc: Andy Shevchenko <andy@infradead.org>
2018-07-20 05:27:43 +07:00
|
|
|
int __pci_hp_initialize(struct hotplug_slot *slot, struct pci_bus *bus, int nr,
|
|
|
|
|
const char *name, struct module *owner,
|
|
|
|
|
const char *mod_name);
|
|
|
|
|
int pci_hp_add(struct hotplug_slot *slot);
|
|
|
|
|
|
|
|
|
|
void pci_hp_del(struct hotplug_slot *slot);
|
|
|
|
|
void pci_hp_destroy(struct hotplug_slot *slot);
|
|
|
|
|
void pci_hp_deregister(struct hotplug_slot *slot);
|
|
|
|
|
|
2011-05-27 20:02:11 +07:00
|
|
|
/* use a define to avoid include chaining to get THIS_MODULE & friends */
|
|
|
|
|
#define pci_hp_register(slot, pbus, devnr, name) \
|
|
|
|
|
__pci_hp_register(slot, pbus, devnr, name, THIS_MODULE, KBUILD_MODNAME)
|
PCI: hotplug: Demidlayer registration with the core
When a hotplug driver calls pci_hp_register(), all steps necessary for
registration are carried out in one go, including creation of a kobject
and addition to sysfs. That's a problem for pciehp once it's converted
to enable/disable the slot exclusively from the IRQ thread: The thread
needs to be spawned after creation of the kobject (because it uses the
kobject's name), but before addition to sysfs (because it will handle
enable/disable requests submitted via sysfs).
pci_hp_deregister() does offer a ->release callback that's invoked
after deletion from sysfs and before destruction of the kobject. But
because pci_hp_register() doesn't offer a counterpart, hotplug drivers'
->probe and ->remove code becomes asymmetric, which is error prone
as recently discovered use-after-free bugs in pciehp's ->remove hook
have shown.
In a sense, this appears to be a case of the midlayer antipattern:
"The core thesis of the "midlayer mistake" is that midlayers are
bad and should not exist. That common functionality which it is
so tempting to put in a midlayer should instead be provided as
library routines which can [be] used, augmented, or ignored by
each bottom level driver independently. Thus every subsystem
that supports multiple implementations (or drivers) should
provide a very thin top layer which calls directly into the
bottom layer drivers, and a rich library of support code that
eases the implementation of those drivers. This library is
available to, but not forced upon, those drivers."
-- Neil Brown (2009), https://lwn.net/Articles/336262/
The presence of midlayer traits in the PCI hotplug core might be ascribed
to its age: When it was introduced in February 2002, the blessings of a
library approach might not have been well known:
https://git.kernel.org/tglx/history/c/a8a2069f432c
For comparison, the driver core does offer split functions for creating
a kobject (device_initialize()) and addition to sysfs (device_add()) as
an alternative to carrying out everything at once (device_register()).
This was introduced in October 2002:
https://git.kernel.org/tglx/history/c/8b290eb19962
The odd ->release callback in the PCI hotplug core was added in 2003:
https://git.kernel.org/tglx/history/c/69f8d663b595
Clearly, a library approach would not force every hotplug driver to
implement a ->release callback, but rather allow the driver to remove
the sysfs files, release its data structures and finally destroy the
kobject. Alternatively, a driver may choose to remove everything with
pci_hp_deregister(), then release its data structures.
To this end, offer drivers pci_hp_initialize() and pci_hp_add() as a
split-up version of pci_hp_register(). Likewise, offer pci_hp_del()
and pci_hp_destroy() as a split-up version of pci_hp_deregister().
Eliminate the ->release callback and move its code into each driver's
teardown routine.
Declare pci_hp_deregister() void, in keeping with the usual kernel
pattern that enablement can fail, but disablement cannot. It only
returned an error if the caller passed in a NULL pointer or a slot which
has never or is no longer registered or is sharing its name with another
slot. Those would be bugs, so WARN about them. Few hotplug drivers
actually checked the return value and those that did only printed a
useless error message to dmesg. Remove that.
For most drivers the conversion was straightforward since it doesn't
matter whether the code in the ->release callback is executed before or
after destruction of the kobject. But in the case of ibmphp, it was
unclear to me whether setting slot_cur->ctrl and slot_cur->bus_on to
NULL needs to happen before the kobject is destroyed, so I erred on
the side of caution and ensured that the order stays the same. Another
nontrivial case is pnv_php, I've found the list and kref logic difficult
to understand, however my impression was that it is safe to delete the
list element and drop the references until after the kobject is
destroyed.
Signed-off-by: Lukas Wunner <lukas@wunner.de>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Acked-by: Andy Shevchenko <andy.shevchenko@gmail.com> # drivers/platform/x86
Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
Cc: Len Brown <lenb@kernel.org>
Cc: Scott Murray <scott@spiteful.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: Sebastian Ott <sebott@linux.vnet.ibm.com>
Cc: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Cc: Corentin Chary <corentin.chary@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>
Cc: Andy Shevchenko <andy@infradead.org>
2018-07-20 05:27:43 +07:00
|
|
|
#define pci_hp_initialize(slot, bus, nr, name) \
|
|
|
|
|
__pci_hp_initialize(slot, bus, nr, name, THIS_MODULE, KBUILD_MODNAME)
|
2009-06-16 09:01:25 +07:00
|
|
|
|
2006-03-04 01:16:05 +07:00
|
|
|
#ifdef CONFIG_ACPI
|
2013-12-03 07:49:16 +07:00
|
|
|
#include <linux/acpi.h>
|
2018-05-24 05:24:08 +07:00
|
|
|
bool pciehp_is_native(struct pci_dev *bridge);
|
2018-05-24 05:32:23 +07:00
|
|
|
int acpi_get_hp_hw_control_from_firmware(struct pci_dev *bridge);
|
2018-05-31 23:42:11 +07:00
|
|
|
bool shpchp_is_native(struct pci_dev *bridge);
|
2008-12-17 10:09:12 +07:00
|
|
|
int acpi_pci_check_ejectable(struct pci_bus *pbus, acpi_handle handle);
|
2009-09-11 01:34:09 +07:00
|
|
|
int acpi_pci_detect_ejectable(acpi_handle handle);
|
2009-09-15 05:35:20 +07:00
|
|
|
#else
|
2018-05-25 03:10:21 +07:00
|
|
|
static inline int acpi_get_hp_hw_control_from_firmware(struct pci_dev *bridge)
|
|
|
|
|
{
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
2018-05-24 05:24:08 +07:00
|
|
|
static inline bool pciehp_is_native(struct pci_dev *bridge) { return true; }
|
2018-05-31 23:42:11 +07:00
|
|
|
static inline bool shpchp_is_native(struct pci_dev *bridge) { return true; }
|
2006-03-04 01:16:05 +07:00
|
|
|
#endif
|
2018-05-28 19:47:52 +07:00
|
|
|
|
|
|
|
|
static inline bool hotplug_is_native(struct pci_dev *bridge)
|
|
|
|
|
{
|
|
|
|
|
return pciehp_is_native(bridge) || shpchp_is_native(bridge);
|
|
|
|
|
}
|
2005-04-17 05:20:36 +07:00
|
|
|
#endif
|