Home
last modified time | relevance | path

Searched +full:hot +full:- +full:plug (Results 1 – 25 of 34) sorted by relevance

12

/Documentation/admin-guide/mm/
Dmemory-hotplug.rst2 Memory Hot(Un)Plug
5 This document describes generic Linux support for memory hot(un)plug with
13 Memory hot(un)plug allows for increasing and decreasing the size of physical
18 Memory hot(un)plug is used for various purposes:
20 - The physical memory available to a machine can be adjusted at runtime, up- or
25 - Replacing hardware, such as DIMMs or whole NUMA nodes, without downtime. One
28 - Reducing energy consumption either by physically unplugging memory modules or
31 Further, the basic memory hot(un)plug infrastructure in Linux is nowadays also
32 used to expose persistent memory, other performance-differentiated memory and
35 Linux only supports memory hot(un)plug on selected 64 bit architectures, such as
[all …]
/Documentation/driver-api/
Dvfio-mediated-device.rst1 .. SPDX-License-Identifier: GPL-2.0-only
17 The number of use cases for virtualizing DMA devices that do not have built-in
25 an IOMMU/device-agnostic framework for exposing direct device access to user
26 space in a secure, IOMMU-protected environment. This framework is used for
44 The following high-level block diagram shows the main components and interfaces
48 +---------------+
50 | +-----------+ | mdev_register_driver() +--------------+
51 | | | +<------------------------+ |
53 | | bus | +------------------------>+ vfio_mdev.ko |<-> VFIO user
55 | | | | +--------------+
[all …]
/Documentation/devicetree/bindings/media/i2c/
Dadv7604.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hans Verkuil <hverkuil-cisco@xs4all.nl>
23 - enum:
24 - adi,adv7610
25 - adi,adv7611
26 - adi,adv7612
32 reg-names:
35 - const: main
[all …]
/Documentation/PCI/
Dacpi-info.rst1 .. SPDX-License-Identifier: GPL-2.0
39 If the OS is expected to manage a non-discoverable device described via
50 These are all device-specific, non-architected things, so the only way a
52 the device-specific details. The host bridge registers also include ECAM
66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
67 With the exception of ECAM, the bridge register space is device-specific
78 PNP0C02 "motherboard" devices are basically a catch-all. There's no
89 the address space is device-specific. An ACPI OS learns the base address
92 The MCFG table must describe the ECAM space of non-hot pluggable host
95 hot-pluggable host bridge [9]. Note that for both MCFG and _CBA, the base
[all …]
Dsysfs-pci.rst1 .. SPDX-License-Identifier: GPL-2.0
11 |-- 0000:17:00.0
12 | |-- class
13 | |-- config
14 | |-- device
15 | |-- enable
16 | |-- irq
17 | |-- local_cpus
18 | |-- remove
19 | |-- resource
[all …]
Dpciebus-howto.rst1 .. SPDX-License-Identifier: GPL-2.0
22 A PCI Express Port is a logical PCI-PCI Bridge structure. There
45 Express Port is a PCI-PCI Bridge device with multiple distinct
48 service drivers will compete for a single PCI-PCI Bridge device.
50 driver is loaded first, it claims a PCI-PCI Bridge Root Port. The
53 drivers load and run on a PCI-PCI Bridge device simultaneously
62 - Allow multiple service drivers to run simultaneously on
63 a PCI-PCI Bridge Port device.
65 - Allow service drivers implemented in an independent
68 - Allow one service driver to run on multiple PCI-PCI Bridge
[all …]
/Documentation/devicetree/bindings/display/panel/
Dpanel-common.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/panel/panel-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
24 width-mm:
29 height-mm:
43 non-descriptive information. For instance an LCD panel in a system that
55 panel-timing:
[all …]
/Documentation/devicetree/bindings/pci/
Dbaikal,bt1-pcie.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/baikal,bt1-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Baikal-T1 PCIe Root Port Controller
10 - Serge Semin <fancer.lancer@gmail.com>
13 Embedded into Baikal-T1 SoC Root Complex controller with a single port
14 activated. It's based on the DWC RC PCIe v4.60a IP-core, which is configured
18 performed by software. There four in- and four outbound iATU regions
22 - $ref: /schemas/pci/snps,dw-pcie.yaml#
[all …]
Dsnps,dw-pcie-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
23 Interface - DBI. In accordance with the reference manual the register
24 configuration space belongs to the Configuration-Dependent Module (CDM)
25 and is split up into several sub-parts Standard PCIe configuration
26 space, Port Logic Registers (PL), Shadow Config-space Registers,
[all …]
Dsnps,dw-pcie.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Root Port controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie
23 - compatible
[all …]
/Documentation/dev-tools/
Dkselftest.rst23 On some systems, hot-plug tests could hang forever waiting for cpu and
24 memory to be ready to be offlined. A special hot-plug target is created
25 to run the full range of hot-plug tests. In default mode, hot-plug tests run
26 in safe mode with a limited scope. In limited mode, cpu-hotplug test is
40 $ make -C tools/testing/selftests
44 $ make -C tools/testing/selftests run_tests
87 $ make -C tools/testing/selftests TARGETS=ptrace run_tests
106 $ make -C tools/testing/selftests SKIP_TARGETS=ptrace run_tests
117 See the top-level tools/testing/selftests/Makefile for the list of all
125 $ make -C tools/testing/selftests hotplug
[all …]
/Documentation/driver-api/driver-model/
Doverview.rst16 bus-specific drivers for bridges and devices by consolidating a set of data
19 Traditional driver models implemented some sort of tree-like structure
30 computer: namely the ability to do seamless device "plug and play", power
31 management, and hot plug. In particular, the model dictated by Intel and
33 on an x86-compatible system can work within this paradigm. Of course,
43 and sometimes by the device-specific drivers.
93 The auto-mounting of sysfs is typically accomplished by an entry similar to
98 or something similar in the /lib/init/fstab file on Debian-based systems::
104 # mount -t sysfs sysfs /sys
107 This directory may be populated at each layer of discovery - the global layer,
[all …]
/Documentation/ABI/testing/
Dsysfs-devices-memory7 added or removed dynamically to represent hot-add/remove
10 http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils
21 http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils
22 lsmem/chmem part of util-linux
29 is read-only; it is a legacy interface only ever used on s390x
31 Users: Legacy s390-tools lsmem/chmem
38 is read-only and contains the section ID in hexadecimal
47 is read-write. When read, it returns the online/offline
67 http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils
75 read-only.
[all …]
/Documentation/arch/s390/
Dvfio-ap.rst13 The AP adapter cards are exposed via the AP bus. The motivation for vfio-ap
45 sub-directory::
76 significant bit, correspond to domains 0-255.
111 * NQAP: to enqueue an AP command-request message to a queue
112 * DQAP: to dequeue an AP command-reply message from a queue
132 an APID from 0-255. If a bit is set, the corresponding adapter is valid for
137 corresponds to an AP queue index (APQI) from 0-255. If a bit is set, the
142 changed by an AP command-request message sent to a usage domain from the
144 0-255. If a bit is set, the corresponding domain can be modified by an AP
145 command-request message sent to a usage domain.
[all …]
/Documentation/devicetree/bindings/pinctrl/
Dqcom,sc7180-pinctrl.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/qcom,sc7180-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <andersson@kernel.org>
11 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
18 const: qcom,sc7180-pinctrl
23 reg-names:
25 - const: west
26 - const: north
[all …]
/Documentation/infiniband/
Dcore_locking.rst7 both low-level drivers that sit below the midlayer and upper level
13 With the following exceptions, a low-level driver implementation of
17 - create_ah
18 - modify_ah
19 - query_ah
20 - destroy_ah
21 - post_send
22 - post_recv
23 - poll_cq
24 - req_notify_cq
[all …]
/Documentation/scsi/
DChangeLog.ips4 5.00.01 - Sarasota ( 5i ) adapters must always be scanned first
5 - Get rid on IOCTL_NEW_COMMAND code
6 - Add Extended DCDB Commands for Tape Support in 5I
8 4.90.11 - Don't actually RESET unless it's physically required
9 - Remove unused compile options
11 4.90.08 - Data Corruption if First Scatter Gather Element is > 64K
13 4.90.08 - Increase Delays in Flashing ( Trombone Only - 4H )
15 4.90.05 - Use New PCI Architecture to facilitate Hot Plug Development
17 4.90.01 - Add ServeRAID Version Checking
19 4.80.26 - Clean up potential code problems ( Arjan's recommendations )
[all …]
/Documentation/mm/
Dmemory-model.rst1 .. SPDX-License-Identifier: GPL-2.0
23 Regardless of the selected memory model, there exists one-to-one
35 non-NUMA systems with contiguous, or mostly contiguous, physical
54 straightforward: `PFN - ARCH_PFN_OFFSET` is an index to the
65 as hot-plug and hot-remove of the physical memory, alternative memory
66 maps for non-volatile memory devices and deferred initialization of
85 NR\_MEM\_SECTIONS = 2 ^ {(MAX\_PHYSMEM\_BITS - SECTION\_SIZE\_BITS)}
87 The `mem_section` objects are arranged in a two-dimensional array
104 corresponding `struct page` - a "classic sparse" and "sparse
108 The classic sparse encodes the section number of a page in page->flags
[all …]
/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/
Doverview.rst16 DPAA2 is a hardware architecture designed for high-speeed network
23 DPAA2 hardware resources. The MC provides an object-based abstraction for
28 The MC provides memory-mapped I/O command interfaces (MC portals)
34 +--------------------------------------+
38 +-----------------------------|--------+
44 +------------------------| mc portal |-+
46 | +- - - - - - - - - - - - -V- - -+ |
50 | +- - - - - - - - - - - - - - - -+ |
54 | --------- ------- |
55 | -queues -DPRC |
[all …]
/Documentation/devicetree/bindings/display/samsung/
Dsamsung,exynos-hdmi.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/display/samsung/samsung,exynos-hdmi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Inki Dae <inki.dae@samsung.com>
11 - Seung-Woo Kim <sw0312.kim@samsung.com>
12 - Kyungmin Park <kyungmin.park@samsung.com>
13 - Krzysztof Kozlowski <krzk@kernel.org>
18 - samsung,exynos4210-hdmi
19 - samsung,exynos4212-hdmi
[all …]
/Documentation/PCI/endpoint/
Dpci-endpoint.rst1 .. SPDX-License-Identifier: GPL-2.0
15 vendor ID, device ID), support other services like hot-plug, power management,
22 validation, co-processor accelerator, etc.
32 ------------------------------------
53 * raise_irq: ops to raise a legacy, MSI or MSI-X interrupt
107 Legacy Interrupt, MSI or MSI-X Interrupt.
124 the EPF device with EPC device. pci-ep-cfs.c can be used as reference for
158 ----------------------------------
212 pci-ep-cfs.c can be used as reference for using these APIs.
/Documentation/core-api/
Dcpu_hotplug.rst18 support NUMA hardware which are hot pluggable as well, where physical node
26 A more novel use of CPU-hotplug support is its use today in suspend resume
27 support for SMP. Dual-core and HT support makes even a laptop run SMP kernels
75 from the map depending on the event is hot-add/hot-remove. There are currently
80 be read-only for most use. When setting up per-cpu resources almost always use
94 $ ls -lh /sys/devices/system/cpu
96 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu0
97 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu1
98 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu2
99 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu3
[all …]
/Documentation/networking/
Dsfp-phylink.rst1 .. SPDX-License-Identifier: GPL-2.0
10 phylink is a mechanism to support hot-pluggable networking modules
11 directly connected to a MAC without needing to re-initialise the
12 adapter on hot-plug events.
14 phylink supports conventional phylib-based setups, fixed link setups
35 3. In-band mode
37 In-band mode is used with 802.3z, SGMII and similar interface modes,
38 and we are expecting to use and honor the in-band negotiation or
43 .. code-block:: none
47 phy-mode = "sgmii";
[all …]
/Documentation/admin-guide/
Dthunderbolt.rst1 .. SPDX-License-Identifier: GPL-2.0
25 -----------------------------------
27 should be a userspace tool that handles all the low-level details, keeps
31 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
35 ``/etc/udev/rules.d/99-local.rules``::
102 -----------------------------------------------------------------
105 /sys/bus/thunderbolt/devices/0-1/authorized - 0
106 /sys/bus/thunderbolt/devices/0-1/device - 0x8004
107 /sys/bus/thunderbolt/devices/0-1/device_name - Thunderbolt to FireWire Adapter
108 /sys/bus/thunderbolt/devices/0-1/vendor - 0x1
[all …]
/Documentation/arch/powerpc/
Deeh-pci-error-recovery.rst11 ---------
12 The IBM POWER-based pSeries and iSeries computers include PCI bus
22 a CPU machine-check/check-stop condition, halting the CPU entirely.
30 Future systems from other vendors, based on the PCI-E specification,
35 --------------------
51 connectivity due to a poorly seated card), and PCI-X split-completion
54 physically removing and re-seating the PCI card.
58 ----------------------
72 return all-ff's (0xff, 0xffff, 0xffffffff for 8/16/32-bit reads).
80 into the firmware are referred to as RTAS (Run-Time Abstraction
[all …]

12