Home
last modified time | relevance | path

Searched +full:cpu +full:- +full:release +full:- +full:addr (Results 1 – 15 of 15) sorted by relevance

/Documentation/devicetree/bindings/arm/
Dcpus.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
14 the "cpus" node, which in turn contains a number of subnodes (ie "cpu")
15 defining properties for every cpu.
17 Bindings for CPU nodes follow the Devicetree Specification, available from:
21 with updates for 32-bit and 64-bit ARM systems provided in this document.
30 - square brackets define bitfields, eg reg[7:0] value of the bitfield in
34 cpus and cpu node bindings definition
[all …]
/Documentation/devicetree/bindings/cpu/
Dcpu-topology.txt2 CPU topology binding description
6 1 - Introduction
12 - socket
13 - cluster
14 - core
15 - thread
18 symmetric multi-threading (SMT) is supported or not.
20 For instance in a system where CPUs support SMT, "cpu" nodes represent all
22 In systems where SMT is not supported "cpu" nodes represent all cores present
25 CPU topology bindings allow one to associate cpu nodes with hierarchical groups
[all …]
/Documentation/translations/zh_CN/arm64/
Dbooting.txt12 ---------------------------------------------------------------------
26 ---------------------------------------------------------------------
36 AArch64 异常模型由多个异常级（EL0 - EL3）组成，对于 EL0 和 EL1 异常级
41 这个术语来定义在将控制权交给 Linux 内核前 CPU 上执行的所有软件。
54 -----------------
65 ---------------
77 -------------
87 -------------
107 - 自 v3.17 起，除非另有说明，所有域都是小端模式。
109 - code0/code1 负责跳转到 stext.
[all …]
/Documentation/arm64/
Dbooting.rst13 (EL0 - EL3), with EL0 and EL1 having a secure and a non-secure
14 counterpart. EL2 is the hypervisor level and exists only in non-secure
18 simply to define all software that executes on the CPU(s) before control
33 ---------------------------
46 -------------------------
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
59 ------------------------------
71 ------------------------
75 The decompressed kernel image contains a 64-byte header as follows::
91 - As of v3.17, all fields are little endian unless stated otherwise.
[all …]
/Documentation/translations/ko_KR/
Dmemory-barriers.txt2 This is a version of Documentation/memory-barriers.txt translated into Korean.
15 Documentation/memory-barriers.txt
39 일부 이상한 점들은 공식적인 메모리 일관성 모델과 tools/memory-model/ 에 있는
60 해당 배리어의 명시적 사용이 불필요해서 no-op 이 될수도 있음을 알아두시기
76 - 디바이스 오퍼레이션.
77 - 보장사항.
81 - 메모리 배리어의 종류.
82 - 메모리 배리어에 대해 가정해선 안될 것.
83 - 데이터 의존성 배리어 (역사적).
84 - 컨트롤 의존성.
[all …]
/Documentation/core-api/
Datomic_ops.rst23 See :ref:`Documentation/process/volatile-considered-harmful.rst
26 local_t is very similar to atomic_t. If the counter is per CPU and only
27 updated by one CPU, local_t is probably more appropriate. Please see
28 :ref:`Documentation/core-api/local_ops.rst <local_ops>` for the semantics of
35 #define atomic_set(v, i) ((v)->counter = (i))
59 return -ENOMEM;
60 atomic_set(&k->counter, 0);
70 #define atomic_read(v) ((v)->counter)
155 variable a is set at boot time before the second CPU is brought online
179 Don't even -think- about doing this without proper use of memory barriers,
[all …]
/Documentation/virt/kvm/devices/
Ds390_flic.txt4 FLIC handles floating (non per-cpu) interrupts, i.e. I/O, service and some
5 machine check interruptions. All interrupts are stored in a per-vm list of
11 - add interrupts (KVM_DEV_FLIC_ENQUEUE)
12 - inspect currently pending interrupts (KVM_FLIC_GET_ALL_IRQS)
13 - purge all pending floating interrupts (KVM_DEV_FLIC_CLEAR_IRQS)
14 - purge one pending floating I/O interrupt (KVM_DEV_FLIC_CLEAR_IO_IRQ)
15 - enable/disable for the guest transparent async page faults
16 - register and modify adapter interrupt sources (KVM_DEV_FLIC_ADAPTER_*)
17 - modify AIS (adapter-interruption-suppression) mode state (KVM_DEV_FLIC_AISM)
18 - inject adapter interrupts on a specified adapter (KVM_DEV_FLIC_AIRQ_INJECT)
[all …]
/Documentation/powerpc/
Dfirmware-assisted-dump.rst2 Firmware-Assisted Dump
7 The goal of firmware-assisted dump is to enable the dump of
8 a crashed system, and to do so from a fully-reset system, and
12 - Firmware-Assisted Dump (FADump) infrastructure is intended to replace
14 - Fadump uses the same firmware interfaces and memory reservation model
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
19 - Unlike phyp dump, userspace tool does not need to refer any sysfs
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
23 - Once enabled through kernel boot parameter, FADump can be
28 Comparing with kdump or other strategies, firmware-assisted
[all …]
/Documentation/
Dmemory-barriers.txt19 documentation at tools/memory-model/. Nevertheless, even this memory
37 Note also that it is possible that a barrier may be a no-op for an
48 - Device operations.
49 - Guarantees.
53 - Varieties of memory barrier.
54 - What may not be assumed about memory barriers?
55 - Data dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
58 - Examples of memory barrier sequences.
[all …]
/Documentation/ia64/
Derr_inject.rst39 #cpu, loop, interval, err_type_info, err_struct_info, err_data_buffer
41 # cpu: logical cpu number the error will be inject in.
50 #corrected, data cache, hier-2, physical addr(assigned by tool code).
55 #corrected, data cache, hier-2, physical addr(assigned by tool code).
60 #recoverable, DTR0, hier-2.
111 #define ERR_DATA_BUFFER_SIZE 3 // Three 8-byte.
114 #define PATH_FORMAT "/sys/devices/system/cpu/cpu%d/err_inject/"
121 int log_info(int cpu, const char *fmt, ...)
128 sprintf(fn, "%d.log", cpu);
132 return -1;
[all …]
/Documentation/filesystems/nfs/
Dnfs-rdma.txt12 - Overview
13 - Getting Help
14 - Installation
15 - Check RDMA and NFS Setup
16 - NFS/RDMA Setup
25 was first included in the following release, Linux 2.6.25.
28 wire bandwidth at minimal client CPU) under many workloads. The code passes
37 nfs-rdma-devel@lists.sourceforge.net
47 - Install an RDMA device
51 Testing has been performed using several Mellanox-based IB cards, the
[all …]
/Documentation/gpu/
Ddrm-mm.rst6 frame buffers, textures, vertices and other graphics-related data. Given
13 manager to be developed and tried to be a one-size-fits-them all
20 GEM started as an Intel-sponsored project in reaction to TTM's
22 providing a solution to every graphics memory-related problems, GEM
34 ------------------
49 .. code-block:: c
56 void (*release) (struct drm_global_reference *);
64 sizeof(struct ttm_mem_global), and the init and release hooks should
65 point at your driver-specific init and release routines, which probably
74 ttm_bo_global). Again, driver-specific init and release functions may
[all …]
/Documentation/dev-tools/
Dkgdb.rst15 Kdb is simplistic shell-style interface which you can use on a system
22 kernel built-ins or in kernel modules if the code was built with
40 kgdb I/O modules compiled as built-ins or loadable kernel modules in the
46 - In order to enable compilation of kdb, you must first enable kgdb.
48 - The kgdb test compile options are described in the kgdb test suite
52 ------------------------------
55 :menuselection:`Kernel hacking --> Kernel debugging` and select
74 certain regions of the kernel's memory space as read-only. If kgdb
94 -----------------------------
109 If you want to use a PS/2-style keyboard with kdb, you would select
[all …]
/Documentation/admin-guide/
Dras.rst33 -------------
43 * CPU – detect errors at instruction execution and at L1/L2/L3 caches;
47 Self-Monitoring, Analysis and Reporting Technology (SMART).
55 ---------------
68 * **Correctable Error (CE)** - the error detection mechanism detected and
72 * **Uncorrected Error (UE)** - the amount of errors happened above the error
73 correction threshold, and the system was unable to auto-correct.
75 * **Fatal Error** - when an UE error happens on a critical component of the
79 * **Non-fatal Error** - when an UE error happens on an unused component,
80 like a CPU in power down state or an unused memory bank, the system may
[all …]
/Documentation/scsi/
Dncr53c8xx.txt5 95170 DEUIL LA BARRE - FRANCE
57 10.4 PCI configuration fix-up boot option
74 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
75 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
81 18.1 Big Endian CPU
94 Stefan Esser <se@mi.Uni-Koeln.de>
98 - ncr53c8xx generic driver that supports all the SYM53C8XX family including
101 - sym53c8xx enhanced driver (a.k.a. 896 drivers) that drops support of oldest
107 PCI-HOWTO written by Michael Will and in the SCSI-HOWTO written by
118 Useful SCSI tools written by Eric Youngdale are available at tsx-11:
[all …]