| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-devices-online | 6 devices whose bus types provide .online() and .offline()
8 of the device's 'offline' field. If that number is 1 and '0'
10 .offline() callback is executed for the device and (if
11 successful) its 'offline' field is updated accordingly. In
14 for the device and (if successful) its 'offline' field is
17 After a successful execution of the bus type's .offline()
|
| D | sysfs-memory-page-offline | 6 Soft-offline the memory page containing the physical address
9 to soft-offline it, by moving the contents elsewhere or
19 fail the offline. Return value is the size of the
28 Hard-offline the memory page containing the physical
31 kernel will then attempt to hard-offline the page, by
|
| D | usb-uevent | 7 contain ACTION=offline and ERROR=DEAD.
11 KERNEL[130.428945] offline /devices/pci0000:00/0000:00:10.0/usb2 (usb)
12 ACTION=offline
|
| D | sysfs-devices-memory | 47 online/offline state of the memory section. When written,
48 root can toggle the the online/offline state of a removable
52 # echo offline > /sys/devices/system/memory/memoryX/state
58 by root to offline that section.
59 # echo offline > /sys/devices/system/memory/memory22/state
|
| D | sysfs-devices-system-xen_cpu | 16 Interface to online/offline Xen physical cpus
19 to online/offline physical cpus, except cpu0 due to several
|
| D | sysfs-class-remoteproc | 19 "offline"
25 "offline" means the remote processor is powered off.
50 return it to the "offline" state.
|
| /Linux-v5.4/drivers/base/ |
| D | container.c | 24 return cdev->offline ? cdev->offline(cdev) : 0; in container_offline()
31 .offline = container_offline,
|
| D | cpu.c | 134 .offline = cpu_subsys_offline,
246 cpumask_var_t offline; in print_cpus_offline() local
249 if (!alloc_cpumask_var(&offline, GFP_KERNEL)) in print_cpus_offline()
251 cpumask_andnot(offline, cpu_possible_mask, cpu_online_mask); in print_cpus_offline()
252 n = scnprintf(buf, len, "%*pbl", cpumask_pr_args(offline)); in print_cpus_offline()
253 free_cpumask_var(offline); in print_cpus_offline()
270 static DEVICE_ATTR(offline, 0444, print_cpus_offline, NULL);
376 cpu->dev.offline = !cpu_online(num); in register_cpu()
|
| /Linux-v5.4/tools/testing/selftests/memory-hotplug/ |
| D | mem-on-off-test.sh | 53 hotpluggable_memory offline
68 grep -q offline $SYSFS/devices/system/memory/memory$1/state
78 echo offline > $SYSFS/devices/system/memory/memory$1/state
89 echo $FUNCNAME $memory: unexpected offline >&2
117 echo $FUNCNAME $memory: unexpected offline >&2
131 echo $FUNCNAME $memory: unexpected offline >&2
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 68 In this document, this phase is described as online/offline.
76 Unit of Memory online/offline operation
86 unit upon which memory online/offline operations are to be performed. The
158 - at read: contains online/offline state of memory.
161 "online_movable", "online", "offline" command
216 You may have to write it by yourself or online/offline memory by hand.
254 To see (online/offline) state of a memory block, read 'state' file::
260 - If the memory block is offline, you'll read "offline".
274 option. If it is disabled the default is "offline" which means the newly added
282 be hotplugged. Currently offline blocks keep their state. It is possible, under
[all …]
|
| /Linux-v5.4/tools/testing/selftests/cpu-hotplug/ |
| D | cpu-on-off-test.sh | 46 offline_cpus=`cat $SYSFS/devices/system/cpu/offline`
107 echo $FUNCNAME $cpu: unexpected offline >&2
133 echo $FUNCNAME $cpu: unexpected offline >&2
146 echo $FUNCNAME $cpu: unexpected offline >&2
|
| /Linux-v5.4/arch/x86/kernel/ |
| D | topology.c | 75 dev->offline = true; in _debug_hotplug_cpu()
83 dev->offline = false; in _debug_hotplug_cpu()
|
| /Linux-v5.4/drivers/bus/ |
| D | mips_cdmm.c | 268 bool offline; member
366 if (bus->offline) { in mips_cdmm_setup()
374 bus->offline = false; in mips_cdmm_setup()
621 bus->offline = true; in BUILD_PERDEV_HELPER()
649 bus->offline = false; in mips_cdmm_cpu_online()
|
| /Linux-v5.4/Documentation/fault-injection/ |
| D | notifier-error-inject.rst | 44 Example: Inject memory hotplug offline error (-12 == -ENOMEM)::
48 # echo offline > /sys/devices/system/memory/memoryXXX/state
97 These scripts first do simple online and offline tests and then do fault
|
| /Linux-v5.4/Documentation/core-api/ |
| D | memory-hotplug.rst | 34 the memory block that we attempted to offline.
64 - start_pfn is start_pfn of online/offline memory.
65 - nr_pages is # of pages of online/offline memory.
95 - synchronize against online/offline requests (e.g. via sysfs). This way, memory
|
| D | cpu_hotplug.rst | 116 -r--r--r-- 1 root root 4.0K Dec 21 16:33 offline
121 The files *offline*, *online*, *possible*, *present* represent the CPU masks.
126 smpboot: CPU 4 is now offline
141 * Resume from hibernate/suspend. Hibernate/suspend will fail if CPU0 is offline.
150 The offline case
168 It is possible to receive notifications once a CPU is offline or onlined. This
226 goes online (offline) and during initial setup (shutdown) of the driver. However
349 After CPU successfully onlined or offline udev events are sent. A udev rule like: ::
357 if [ "${ACTION}" = "offline" ]
359 echo "CPU ${DEVPATH##*/} offline"
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 24 writing "0" to offline and "1" to online.
99 the CPU offline, then bring it back online. This forces
101 with multiple CPUs, force them all offline before bringing the
103 do not offline any other CPUs, because doing so could force the
115 be de-jittered. (It is OK to force this CPU offline and then
127 be de-jittered. (It is OK to force this CPU offline and then
139 be de-jittered. (It is OK to force this CPU offline and then
184 CPU offline, then bring it back online. This forces recurring
186 CPUs, force them all offline before bringing the first one
188 offline any other CPUs, because doing so could force the timer
|
| D | cputopology.rst | 137 offline: CPUs that are not online because they have been
160 offline: 2,4-31,32-63
167 was manually taken offline (and is the only CPU that can be brought
171 offline: 2,4-127,128-143
|
| /Linux-v5.4/include/linux/ |
| D | container.h | 19 int (*offline)(struct container_dev *cdev); member
|
| /Linux-v5.4/drivers/staging/fieldbus/Documentation/ABI/ |
| D | sysfs-class-fieldbus-dev | 44 Whether the fieldbus is online or offline.
47 '0' meaning 'offline'
|
| /Linux-v5.4/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /Linux-v5.4/Documentation/scsi/ |
| D | scsi_eh.txt | 327 either offline or ready, scsi_eh_finish_cmd() is invoked for
331 Note that both offline and ready status mean that the sdev is
358 If STU succeeds and the sdev is either offline or ready,
386 scmds on all ready or offline sdevs on the channel are
395 all ready or offline sdevs on the host are EH-finished.
401 Take all sdevs which still have unrecovered scmds offline
419 all failed scmds and either ready for new commands or offline. Also,
469 offline.
|
| /Linux-v5.4/Documentation/s390/ |
| D | driver-model.rst | 50 An interface to set the device online and offline.
251 possible). This ccwgroup device can be set online or offline just like a normal
255 again (only when offline). This is a generic ccwgroup mechanism (the driver does
279 - Can be 'online' or 'offline'.
280 Piping 'on' or 'off' sets the chpid logically online/offline.
|
| /Linux-v5.4/drivers/acpi/ |
| D | container.c | 61 cdev->offline = acpi_container_offline; in container_device_attach()
|
| /Linux-v5.4/arch/x86/ras/ |
| D | Kconfig | 8 PFN overflows, we try to soft-offline that page as we take it to mean
|
