| /linux/drivers/pci/hotplug/ |
| H A D | pci_hotplug_core.c | 3 * PCI HotPlug Controller Core
60 retval = get_power_status(pci_slot->hotplug, &value); in GET_STATUS()
70 struct hotplug_slot *slot = pci_slot->hotplug; in power_write_file()
111 retval = get_attention_status(pci_slot->hotplug, &value); in attention_read_file()
121 struct hotplug_slot *slot = pci_slot->hotplug; in attention_write_file()
150 retval = get_latch_status(pci_slot->hotplug, &value); in latch_read_file()
167 retval = get_adapter_status(pci_slot->hotplug, &value); in presence_read_file()
182 struct hotplug_slot *slot = pci_slot->hotplug; in test_write_file()
247 /* Create symbolic link to the hotplug driver module */ in fs_add_slot()
337 * __pci_hp_register - register a hotplug_slot with the PCI hotplug subsystem
[all …]
|
| H A D | rpadlpar_core.c | 103 * find_php_slot - return hotplug slot structure for device node
106 * This routine will return the hotplug slot structure
196 /* Add hotplug slot */ in dlpar_add_pci_slot()
198 printk(KERN_ERR "%s: unable to add hotplug slot %s\n", in dlpar_add_pci_slot()
214 /* If pci slot is hotpluggable, use hotplug to remove it */ in dlpar_remove_phb()
217 printk(KERN_ERR "%s: unable to remove hotplug slot %s\n", in dlpar_remove_phb()
247 printk(KERN_ERR "%s: unable to add hotplug slot %s\n", in dlpar_add_phb()
277 * Make the hotplug module and the kernel aware of a newly added I/O Slot.
325 * Remove the kernel and hotplug representations of an I/O Slot.
350 * Remove the kernel and hotplug representations of a PCI I/O Slot.
[all …]
|
| H A D | pciehp_pci.c | 25 * pciehp_configure_device() - enumerate PCI devices below a hotplug bridge
26 * @ctrl: PCIe hotplug controller
28 * Enumerate PCI devices below a hotplug bridge and add them to the system.
45 * boot firmware or a previous hotplug event. in pciehp_configure_device()
85 * pciehp_unconfigure_device() - remove PCI devices below a hotplug bridge
86 * @ctrl: PCIe hotplug controller
91 * Unbind PCI devices below a hotplug bridge from their drivers and remove
|
| H A D | cpcihp_generic.c | 11 * This generic CompactPCI hotplug driver should allow using the PCI hotplug
76 err("Invalid hotplug bus bridge device bus number"); in validate_parameters()
82 err("Invalid hotplug bus bridge device"); in validate_parameters()
88 err("Invalid hotplug bus bridge device slot number"); in validate_parameters()
154 err("Could not register cPCI hotplug controller"); in cpcihp_generic_init()
161 err("Could not register cPCI hotplug bus"); in cpcihp_generic_init()
168 err("Could not started cPCI hotplug system"); in cpcihp_generic_init()
|
| H A D | acpiphp_glue.c | 3 * ACPI PCI HotPlug glue functions to ACPI CA subsystem
54 * acpiphp_init_context - Create hotplug context and grab a reference to it.
75 * acpiphp_get_context - Get hotplug context and grab a reference to it.
93 * acpiphp_put_context - Drop a reference to ACPI hotplug context.
94 * @context: ACPI hotplug context to drop a reference to.
168 /* Root bridges will not have hotplug context. */ in free_bridge()
259 acpi_handle_err(handle, "No hotplug context\n"); in acpiphp_add_context()
299 * by the native PCIe hotplug (PCIeHP) or standard PCI hotplug in acpiphp_add_context()
313 pr_debug("found ACPI PCI Hotplug slot %llu at PCI %04x:%02x:%02x\n", in acpiphp_add_context()
321 pr_warn("Slot %llu already registered by another hotplug driver\n", sun); in acpiphp_add_context()
[all …]
|
| H A D | acpi_pcihp.c | 34 /* acpi_run_oshp - get control of hotplug from the firmware
36 * @handle - the handle of the hotplug controller.
64 * @pdev: the pci_dev of the bridge that has a hotplug controller
66 * Attempt to take hotplug control from firmware.
108 * This hotplug controller was not listed in the ACPI name in acpi_get_hp_hw_control_from_firmware()
121 pci_info(pdev, "Requesting control of SHPC hotplug via OSHP (%s)\n", in acpi_get_hp_hw_control_from_firmware()
134 pci_info(pdev, "Cannot get control of SHPC hotplug\n"); in acpi_get_hp_hw_control_from_firmware()
138 pci_info(pdev, "Gained control of SHPC hotplug (%s)\n", in acpi_get_hp_hw_control_from_firmware()
|
| H A D | pciehp.h | 47 * struct controller - PCIe hotplug controller
49 * @dsn: cached copy of Device Serial Number of Function 0 in the hotplug slot
77 * @hotplug_slot: structure registered with the PCI hotplug core
81 * @depth: Number of additional hotplug ports in the path to the root bus,
88 * PCIe hotplug has a 1:1 relationship between controller and slot, hence
113 struct hotplug_slot hotplug_slot; /* hotplug core interface */
149 * hotplug port was inaccessible when the interrupt occurred, requiring
151 * hotplug port accessible by runtime resuming its parents to D0
|
| /linux/Documentation/core-api/ |
| H A D | cpu_hotplug.rst | 2 CPU hotplug in the Kernel
19 insertion and removal require support for CPU hotplug.
23 system execution path. Hence the need for CPU hotplug support in the
26 A more novel use of CPU-hotplug support is its use today in suspend resume
73 of them may be online. When physical hotplug is processed by the relevant
77 at which time hotplug is disabled.
87 Using CPU hotplug
104 drwxr-xr-x 2 root root 0 Dec 21 16:33 hotplug
125 and excluded from CPU hotplug.
127 The CPU hotplug coordination
[all …]
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | memory-hotplug.rst | 4 Memory Hotplug
8 memory-hotplug component.
13 2) Hotplug Memory Block size
19 The default-online behavior of hotplug memory is dictated by the following,
36 :code:`ZONE_MOVABLE` attempts to retain the hotplug-ability of a memory block
41 Hotplug Memory Block Size
43 By default, on most architectures, the Hotplug Memory Block Size is either
47 deciding the Hotplug Memory Block Size.
63 will be allocated from the local node of the processor running the hotplug
73 The DAX driver surfaces this memory to memory-hotplug as "Driver Managed". This
|
| H A D | dax-driver.rst | 14 - Engage the memory-hotplug interface to add CXL memory to page allocator.
32 The :code:`dax_kmem` driver converts a `DAX Device` into a series of `hotplug
33 memory blocks` managed by :code:`kernel/memory-hotplug.c`. This capacity
40 hotplug will set aside a portion of the memory block capacity to allocate
43 CPU executing the hotplug operation.
|
| /linux/tools/testing/selftests/sched_ext/ |
| H A D | hotplug.c | 13 #include "hotplug.bpf.skel.h"
45 struct hotplug *skel; in test_hotplug()
101 struct hotplug *skel; in test_hotplug_attach()
109 skel = SCX_OPS_OPEN(hotplug_nocb_ops, hotplug); in test_hotplug_attach()
112 SCX_OPS_LOAD(skel, hotplug_nocb_ops, hotplug, uei); in test_hotplug_attach()
115 * Take the CPU offline to increment the global hotplug seq, which in test_hotplug_attach()
116 * should cause attach to fail due to us setting the hotplug seq above in test_hotplug_attach()
163 .name = "hotplug",
164 .description = "Verify hotplug behavior",
|
| /linux/include/linux/ |
| H A D | pci_hotplug.h | 3 * PCI HotPlug Core Functions
18 * struct hotplug_slot_ops -the callbacks that the hotplug pci core can use
31 * hotplug events or where a slot can be reset independent of the bus.
33 * The table of function pointers that is passed to the hotplug pci core by a
34 * hotplug pci driver. These functions are called by the hotplug pci core when
51 * struct hotplug_slot - used to register a physical slot with the hotplug pci core
60 /* Variables below this are for use only by the hotplug pci core. */
|
| H A D | cpuhotplug.h | 26 * CPU hotplug states. The state machine invokes the installed state
38 * hotplug startup/teardown code with interrupts disabled.
41 * hotplug thread with interrupts and preemption enabled.
195 /* Online section invoked on the hotplugged CPU from the hotplug thread */
261 * cpuhp_setup_state - Setup hotplug state callbacks with calling the @startup
280 * cpuhp_setup_state_cpuslocked - Setup hotplug state callbacks with calling
301 * cpuhp_setup_state_nocalls - Setup hotplug state callbacks without calling the
321 * cpuhp_setup_state_nocalls_cpuslocked - Setup hotplug state callbacks without
426 * cpuhp_remove_state - Remove hotplug state callbacks and invoke the teardown
438 * cpuhp_remove_state_nocalls - Remove hotplug state callbacks without invoking
[all …]
|
| /linux/Documentation/arch/arm64/ |
| H A D | cpu-hotplug.rst | 5 CPU Hotplug and ACPI
8 CPU hotplug in the arm64 world is commonly used to describe the kernel taking
15 CPU Hotplug on physical systems - CPUs not present at boot
42 CPU Hotplug on virtual systems - CPUs not enabled at boot
49 CPU Hotplug on virtual systems is supported. It is distinct from physical
50 CPU Hotplug as all resources are described as ``present``, but CPUs may be
58 Virtual hotplug is implemented as a firmware policy affecting which CPUs can be
|
| /linux/include/linux/platform_data/ |
| H A D | mlxreg.h | 28 * enum mlxreg_hotplug_kind - kind of hotplug entry
57 * enum mlxreg_hotplug_device_action - hotplug device action required for
73 * struct mlxreg_core_hotplug_notifier - hotplug notifier block:
98 * Structure represents I2C hotplug device static data (board topology) and
127 * @hpdev - hotplug device data;
160 * @kind: kind of hotplug attribute;
207 * struct mlxreg_core_hotplug_platform_data - hotplug platform data:
209 * @items: same type components with the hotplug capability;
212 * @count: number of the components with the hotplug capability;
|
| /linux/drivers/platform/mellanox/ |
| H A D | mlxreg-dpu.c | 71 /* Hotplug aggregation masks. */
198 /* Default hotplug data. */
324 * @hotplug_data: hotplug platform data
325 * @hotplug: hotplug device
333 struct platform_device *hotplug; member
464 /* Copy platform specific hotplug data. */ in mlxreg_dpu_config_init()
493 /* Register hotplug driver. */ in mlxreg_dpu_config_init()
497 mlxreg_dpu->hotplug = in mlxreg_dpu_config_init()
498 platform_device_register_resndata(dev, "mlxreg-hotplug", in mlxreg_dpu_config_init()
502 if (IS_ERR(mlxreg_dpu->hotplug)) { in mlxreg_dpu_config_init()
[all …]
|
| /linux/Documentation/admin-guide/media/ |
| H A D | ttusb-dec.rst | 18 - Hotplug firmware loader
38 Hotplug Firmware Loading
44 Copy the three files downloaded above into the /usr/lib/hotplug/firmware or
45 /lib/firmware directory (depending on configuration of firmware hotplug).
|
| /linux/kernel/ |
| H A D | cpu.c | 12 #include <linux/sched/hotplug.h>
49 * struct cpuhp_cpu_state - Per cpu hotplug state storage
52 * @fail: Current CPU hotplug callback state
53 * @thread: Pointer to the hotplug thread
119 * struct cpuhp_step - Hotplug state machine step
166 * Called from cpu hotplug and from the state register machinery.
520 * We can't have hotplug operations before userspace starts running, in lockdep_assert_cpus_held()
521 * and some init codepaths will knowingly not take the hotplug lock. in lockdep_assert_cpus_held()
558 * Wait for currently running CPU hotplug operations to complete (if any) and
559 * disable future CPU hotplug (from sysfs). The 'cpu_add_remove_lock' protects
[all …]
|
| /linux/Documentation/fault-injection/ |
| H A D | notifier-error-inject.rst | 10 * Memory hotplug notifier
33 Memory hotplug notifier error injection module
44 Example: Inject memory hotplug offline error (-12 == -ENOMEM)::
94 * tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh
95 * tools/testing/selftests/memory-hotplug/mem-on-off-test.sh
|
| /linux/drivers/staging/media/av7110/ |
| H A D | Kconfig | 30 download/extract it, and then copy it to /usr/lib/hotplug/firmware
31 or /lib/firmware (depending on configuration of firmware hotplug).
69 download/extract it, and then copy it to /usr/lib/hotplug/firmware
70 or /lib/firmware (depending on configuration of firmware hotplug).
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-acpi | 67 What: /sys/firmware/acpi/hotplug/
71 There are separate hotplug profiles for different classes of
73 processors, PCI root bridges etc. A hotplug profile for a given
75 that class of devices will be handled by the ACPI core hotplug
77 of /sys/firmware/acpi/hotplug/.
80 hotplug profile:
84 hotplug events associated with the given class of
87 effectively disables hotplug for the corresponding
|
| /linux/arch/powerpc/platforms/pseries/ |
| H A D | pmem.c | 13 #include <linux/sched/hotplug.h>
110 /* slim chance, but we might get a hotplug event while booting */ in dlpar_hp_pmem()
114 pr_err("Hotplug event for a pmem device, but none exists\n"); in dlpar_hp_pmem()
119 pr_err("Unsupported hotplug event type %d\n", in dlpar_hp_pmem()
133 pr_err("Unsupported hotplug action (%d)\n", hp_elog->action); in dlpar_hp_pmem()
|
| /linux/drivers/net/wireless/intel/iwlegacy/ |
| H A D | Kconfig | 28 look in the hotplug script /etc/hotplug/firmware.agent to
55 look in the hotplug script /etc/hotplug/firmware.agent to
|
| /linux/arch/arm/mach-mvebu/ |
| H A D | platsmp-a9.c | 46 * in the offline state after using CPU hotplug. in mvebu_cortex_a9_boot_secondary()
59 * When a CPU is brought back online, either through CPU hotplug, or
75 * CPU hotplug is implemented by putting offline CPUs into the in armada_38x_cpu_die()
83 * we support CPU hotplug. However, the function does not need to do
|
| /linux/tools/testing/selftests/ftrace/test.d/ftrace/ |
| H A D | func_hotplug.tc | 3 # description: ftrace - function trace across cpu hotplug
15 echo "We cannot test cpu hotplug in UP environment"
28 echo "We cannot test cpu hotplug with a single cpu online"
|