Lines Matching full:hotplug

4 Memory Hotplug
10 This document is about memory hotplug including how-to-use and current status.
11 Because Memory Hotplug is still under development, contents of this text will
18     (1) x86_64's has special implementation for memory hotplug.
26 Purpose of memory hotplug
29 Memory Hotplug allows users to increase/decrease the amount of memory.
40 Linux memory hotplug is designed for both purpose.
42 Phases of memory hotplug
45 There are 2 phases in Memory Hotplug:
47   1) Physical Memory Hotplug phase
48   2) Logical Memory Hotplug phase.
63 Logical Memory Hotplug phase is to change memory state into
70 Logical Memory Hotplug phase is triggered by write of sysfs file by system
71 administrator. For the hot-add case, it must be executed after Physical Hotplug
73 (However, if you writes udev's hotplug scripts for memory hotplug, these
79 Memory hotplug uses SPARSEMEM memory model which allows memory to be divided
97 To use memory hotplug feature, kernel must be compiled with following
100 - For all memory hotplug:
108 - For ACPI memory hotplug, the following are also necessary:
109     - Memory hotplug (under ACPI Support menu) (``CONFIG_ACPI_HOTPLUG_MEMORY``)
112 - As a related configuration, if your box has a feature of NUMA-node hotplug
123 sysfs files for memory hotplug
136 the existence of one should not affect the hotplug capabilities of the memory
187   These directories/files appear after physical memory hotplug phase.
208 On x86_64/ia64 platform, memory hotplug by ACPI is supported.
210 In general, the firmware (ACPI) which supports memory hotplug defines
212 Linux's ACPI handler does hot-add memory to the system and calls a hotplug udev
215 But scripts for memory hotplug are not contained in generic udev package(now).
220 If firmware supports NUMA-node hotplug, and defines an object _HID "ACPI0004",
222 calls hotplug code for all of objects which are defined in it.
223 If memory device is found, memory hotplug code will be called.
229 hotplug event.  Therefore, the memory "probe" interface is supported to
232 if hotplug is supported, although for x86 this should be handled by ACPI
244 memory_block_size] memory range is hot-added. In this case, hotplug script is
382   Memory hotplug's design direction is to make the possibility of memory
406 - synchronize against CPU hotplug and similar (e.g. relevant for ACPI and PPC)
426 write mode to serialise memory hotplug (e.g. access to global/zone