Home
last modified time | relevance | path

Searched full:system (Results 1 – 25 of 5421) sorted by relevance

12345678910>>...217

/Linux-v5.4/drivers/eisa/
Deisa.ids18 ACE1010 "ACME Super Fast System Board"
26 ACR1201 "Acer 1200 486/25 EISA System Board"
27 ACR1211 "AcerFrame 3000SP33 486/33 EISA System Board"
39 ACR1711 "AcerFrame 1000 486/33 SYSTEM-2"
40 ACR1801 "Acer P43WE EISA System Board"
41 ACR3211 "AcerFrame 3000MP 486 SYSTEM-1"
42 ACR3221 "AcerFrame 486 Series SYSTEM-2"
43 ACR3231 "AcerFrame 486 Series SYSTEM-3"
44 ACR3241 "AcerFrame 486 Series SYSTEM-4"
45 ACR3261 "AcerFrame 3000MP 486 SYSTEM-1"
[all …]
/Linux-v5.4/include/asm-generic/
Dsyscall.h3 * Access to user system call parameters and results
23 * syscall_get_nr - find what system call a task is executing
27 * If @task is executing a system call or is at system call
28 * tracing about to attempt one, returns the system call number.
29 * If @task is not executing a system call, i.e. it's blocked
33 * system call number can be meaningful. If the actual arch value
41 * syscall_rollback - roll back registers after an aborted system call
42 * @task: task of interest, must be in system call exit tracing
45 * It's only valid to call this when @task is stopped for system
48 * the system call from taking place.
[all …]
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-devices-system-cpu1 What: /sys/devices/system/cpu/
10 /sys/devices/system/cpu/cpu#/
12 What: /sys/devices/system/cpu/kernel_max
13 /sys/devices/system/cpu/offline
14 /sys/devices/system/cpu/online
15 /sys/devices/system/cpu/possible
16 /sys/devices/system/cpu/present
35 the system.
40 What: /sys/devices/system/cpu/probe
41 /sys/devices/system/cpu/release
[all …]
Dsysfs-devices-memory1 What: /sys/devices/system/memory
5 The /sys/devices/system/memory contains a snapshot of the
12 What: /sys/devices/system/memory/memoryX/removable
16 The file /sys/devices/system/memory/memoryX/removable
24 What: /sys/devices/system/memory/memoryX/phys_device
28 The file /sys/devices/system/memory/memoryX/phys_device
32 What: /sys/devices/system/memory/memoryX/phys_index
36 The file /sys/devices/system/memory/memoryX/phys_index
41 What: /sys/devices/system/memory/memoryX/state
45 The file /sys/devices/system/memory/memoryX/state
[all …]
Dsysfs-devices-edac1 What: /sys/devices/system/edac/mc/mc*/reset_counters
12 What: /sys/devices/system/edac/mc/mc*/seconds_since_reset
19 What: /sys/devices/system/edac/mc/mc*/mc_name
25 What: /sys/devices/system/edac/mc/mc*/size_mb
31 What: /sys/devices/system/edac/mc/mc*/ue_count
37 increment, since EDAC will panic the system
39 What: /sys/devices/system/edac/mc/mc*/ue_noinfo_count
46 What: /sys/devices/system/edac/mc/mc*/ce_count
54 such information to the system administrator.
56 What: /sys/devices/system/edac/mc/mc*/ce_noinfo_count
[all …]
Dsysfs-devices-power14 space to check if the device is enabled to wake up the system
20 used to activate the system from a sleep state. Such devices
31 For the devices that are not capable of generating system wakeup
33 be enabled to wake up the system from sleep states.
61 with the main suspend/resume thread) during system-wide power
87 the system from sleep states, this attribute is not present.
88 If the device is not enabled to wake up the system from sleep
99 system from sleep states, this attribute is not present. If
100 the device is not enabled to wake up the system from sleep
109 the device might have aborted system transition into a sleep
[all …]
/Linux-v5.4/arch/powerpc/include/asm/
Dipic.h26 #define IPIC_SICFR 0x00 /* System Global Interrupt Configuration Register */
27 #define IPIC_SIVCR 0x04 /* System Global Interrupt Vector Register */
28 #define IPIC_SIPNR_H 0x08 /* System Internal Interrupt Pending Register (HIGH) */
29 #define IPIC_SIPNR_L 0x0C /* System Internal Interrupt Pending Register (LOW) */
30 #define IPIC_SIPRR_A 0x10 /* System Internal Interrupt group A Priority Register */
31 #define IPIC_SIPRR_B 0x14 /* System Internal Interrupt group B Priority Register */
32 #define IPIC_SIPRR_C 0x18 /* System Internal Interrupt group C Priority Register */
33 #define IPIC_SIPRR_D 0x1C /* System Internal Interrupt group D Priority Register */
34 #define IPIC_SIMSR_H 0x20 /* System Internal Interrupt Mask Register (HIGH) */
35 #define IPIC_SIMSR_L 0x24 /* System Internal Interrupt Mask Register (LOW) */
[all …]
/Linux-v5.4/Documentation/admin-guide/pm/
Dsleep-states.rst5 System Sleep States
13 Sleep states are global low-power states of the entire system in which user
14 space code cannot be executed and the overall system activity is significantly
22 the Linux kernel can support up to four system sleep states, including
23 hibernation and up to three variants of system suspend. The sleep states that
31 This is a generic, pure software, light-weight variant of system suspend (also
36 states while the system is suspended.
38 The system is woken up from this state by in-band interrupts, so theoretically
44 deeper system suspend variants to provide reduced resume latency. It is always
54 operating state is lost (the system core logic retains power), so the system can
[all …]
Dstrategies.rst15 One of them is based on using global low-power states of the whole system in
16 which user space code cannot be executed and the overall system activity is
18 kernel puts the system into one of these states when requested by user space
19 and the system stays in it until a special signal is received from one of
21 user space code can run. Because sleep states are global and the whole system
23 :doc:`system-wide power management <system-wide>`.
27 components of the system, as needed, in the working state. In consequence, if
28 this strategy is in use, the working state of the system usually does not
30 a metastate covering a range of different power states of the system in which
37 If all of the system components are active, the system as a whole is regarded as
[all …]
/Linux-v5.4/arch/nds32/include/asm/
Dsyscall.h14 * syscall_get_nr - find what system call a task is executing
18 * If @task is executing a system call or is at system call
19 * tracing about to attempt one, returns the system call number.
20 * If @task is not executing a system call, i.e. it's blocked
24 * system call number can be meaningful. If the actual arch value
36 * syscall_rollback - roll back registers after an aborted system call
37 * @task: task of interest, must be in system call exit tracing
40 * It's only valid to call this when @task is stopped for system
43 * the system call from taking place.
46 * system call instruction was a no-op. The registers containing
[all …]
/Linux-v5.4/Documentation/process/
Dadding-syscalls.rst4 Adding a New System Call
7 This document describes what's involved in adding a new system call to the
12 System Call Alternatives
15 The first thing to consider when adding a new system call is whether one of
16 the alternatives might be suitable instead. Although system calls are the
35 - If you're just exposing runtime system information, a new node in sysfs
43 :manpage:`fcntl(2)` is a multiplexing system call that hides a lot of complexity, so
49 with :manpage:`fcntl(2)`, this system call is a complicated multiplexor so
57 A new system call forms part of the API of the kernel, and has to be supported
63 together with the corresponding follow-up system calls --
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.txt1 Samsung Exynos IOMMU H/W, System MMU (System Memory Management Unit)
3 Samsung's Exynos architecture contains System MMUs that enables scattered
7 System MMU is an IOMMU and supports identical translation table format to
9 permissions, shareability and security protection. In addition, System MMU has
13 System MMUs are in many to one relation with peripheral devices, i.e. single
14 peripheral device might have multiple System MMUs (usually one for each bus
15 master), but one System MMU can handle transactions from only one peripheral
16 device. The relation between a System MMU and the peripheral device needs to be
19 MFC in all Exynos SoCs and FIMD, M2M Scalers and G2D in Exynos5420 has 2 System
21 * MFC has one System MMU on its left and right bus.
[all …]
/Linux-v5.4/Documentation/ABI/stable/
Dsysfs-devices-node1 What: /sys/devices/system/node/possible
7 What: /sys/devices/system/node/online
13 What: /sys/devices/system/node/has_normal_memory
19 What: /sys/devices/system/node/has_cpu
25 What: /sys/devices/system/node/has_high_memory
32 What: /sys/devices/system/node/nodeX
40 What: /sys/devices/system/node/nodeX/cpumap
46 What: /sys/devices/system/node/nodeX/cpulist
52 What: /sys/devices/system/node/nodeX/meminfo
59 What: /sys/devices/system/node/nodeX/numastat
[all …]
/Linux-v5.4/drivers/soc/renesas/
DKconfig49 #comment "Renesas ARM SoCs System Type"
241 bool "RZ/G1M System Controller support" if COMPILE_TEST
245 bool "RZ/G1E System Controller support" if COMPILE_TEST
249 bool "RZ/G1C System Controller support" if COMPILE_TEST
253 bool "RZ/G2M System Controller support" if COMPILE_TEST
257 bool "RZ/G2E System Controller support" if COMPILE_TEST
261 bool "R-Car H1 System Controller support" if COMPILE_TEST
265 bool "R-Car H2 System Controller support" if COMPILE_TEST
269 bool "R-Car M2-W/N System Controller support" if COMPILE_TEST
273 bool "R-Car V2H System Controller support" if COMPILE_TEST
[all …]
/Linux-v5.4/Documentation/admin-guide/
Dinitrd.rst9 This RAM disk can then be mounted as the root file system and programs
10 can be run from it. Afterwards, a new root file system can be mounted
14 initrd is mainly designed to allow system startup to occur in two phases,
25 When using initrd, the system typically boots as follows:
38 6) init mounts the "real" root file system
39 7) init places the root file system at the root directory using the
40 pivot_root system call
43 9) the initrd file system is removed
65 the "normal" root file system is mounted. initrd data can be read
67 in this case and doesn't necessarily have to be a file system image.
[all …]
/Linux-v5.4/Documentation/userspace-api/
Dseccomp_filter.rst8 A large number of system calls are exposed to every userland process
10 As system calls change and mature, bugs are found and eradicated. A
12 of available system calls. The resulting set reduces the total kernel
13 surface exposed to the application. System call filtering is meant for
17 incoming system calls. The filter is expressed as a Berkeley Packet
19 operated on is related to the system call being made: system call
20 number and the system call arguments. This allows for expressive
21 filtering of system calls using a filter program language with a long
25 to time-of-check-time-of-use (TOCTOU) attacks that are common in system
27 pointers which constrains all filters to solely evaluating the system
[all …]
/Linux-v5.4/Documentation/driver-api/pm/
Ddevices.rst30 This writeup gives an overview of how drivers interact with system-wide
42 System Sleep model:
44 Drivers can enter low-power states as part of entering system-wide
54 Some drivers can manage hardware wakeup events, which make the system
59 whole system enter low-power states more often.
63 Devices may also be put into low-power states while the system is
70 states at run time may require special handling during system-wide power
75 the PM core are involved in runtime power management. As in the system
81 very system-specific, and often device-specific. Also, that if enough devices
83 to entering some system-wide low-power state (system sleep) ... and that
[all …]
/Linux-v5.4/arch/m68k/include/asm/
Dmcfpit.h25 #define MCFPIT_PCSR_CLK1 0x0000 /* System clock divisor */
26 #define MCFPIT_PCSR_CLK2 0x0100 /* System clock divisor */
27 #define MCFPIT_PCSR_CLK4 0x0200 /* System clock divisor */
28 #define MCFPIT_PCSR_CLK8 0x0300 /* System clock divisor */
29 #define MCFPIT_PCSR_CLK16 0x0400 /* System clock divisor */
30 #define MCFPIT_PCSR_CLK32 0x0500 /* System clock divisor */
31 #define MCFPIT_PCSR_CLK64 0x0600 /* System clock divisor */
32 #define MCFPIT_PCSR_CLK128 0x0700 /* System clock divisor */
33 #define MCFPIT_PCSR_CLK256 0x0800 /* System clock divisor */
34 #define MCFPIT_PCSR_CLK512 0x0900 /* System clock divisor */
[all …]
/Linux-v5.4/Documentation/admin-guide/mm/
Dnumaperf.rst12 A system supports such heterogeneous memory by grouping each memory type
47 # symlinks -v /sys/devices/system/node/nodeX/access0/targets/
48 relative: /sys/devices/system/node/nodeX/access0/targets/nodeY -> ../../nodeY
50 # symlinks -v /sys/devices/system/node/nodeY/access0/initiators/
51 relative: /sys/devices/system/node/nodeY/access0/initiators/nodeX -> ../../nodeX
65 the system provides these attributes, the kernel exports them under the
69 /sys/devices/system/node/nodeY/access0/initiators/
77 # tree -P "read*|write*" /sys/devices/system/node/nodeY/access0/initiators/
78 /sys/devices/system/node/nodeY/access0/initiators/
95 System memory may be constructed in a hierarchy of elements with various
[all …]
/Linux-v5.4/Documentation/power/
Dsuspend-and-interrupts.rst2 System Suspend and Device Interrupts
12 Device interrupt request lines (IRQs) are generally disabled during system
29 Device IRQs are re-enabled during system resume, right before the "early" phase
37 There are interrupts that can legitimately trigger during the entire system
47 interrupt will wake the system from a suspended state -- for such cases it is
58 System Wakeup Interrupts, enable_irq_wake() and disable_irq_wake()
61 System wakeup interrupts generally need to be configured to wake up the system
67 during system sleep so as to trigger a system wakeup when needed. For example,
69 handling system wakeup events. Then, if a given interrupt line is supposed to
70 wake up the system from sleep sates, the corresponding input of that interrupt
[all …]
/Linux-v5.4/Documentation/crypto/
Duserspace-if.rst62 send()/write() system call family. The result of the cipher operation is
63 obtained with the read()/recv() system call family.
77 3. Invoke accept with the socket descriptor. The accept system call
80 system calls to send data to the kernel or obtain data from the
88 the input buffer used for the send/write system call and the output
89 buffer used by the read/recv system call may be one and the same. This
120 Using the send() system call, the application provides the data that
121 should be processed with the message digest. The send system call allows
124 - MSG_MORE: If this flag is set, the send system call acts like a
126 calculated. If the flag is not set, the send system call calculates
[all …]
/Linux-v5.4/tools/testing/selftests/rcutorture/bin/
Dfunctions.sh123 qemu-system-x86_64|qemu-system-i386)
126 qemu-system-aarch64)
147 echo qemu-system-x86_64
150 echo qemu-system-i386
153 echo qemu-system-aarch64
156 echo qemu-system-ppc64
160 # Usually this will be one of /usr/bin/qemu-system-*
174 qemu-system-x86_64|qemu-system-i386)
177 qemu-system-aarch64)
196 qemu-system-x86_64)
[all …]
/Linux-v5.4/fs/nls/
DKconfig25 The default NLS used when mounting file system. Note, that this is
27 system (if different) to store data (filenames) on a disk.
43 The Microsoft FAT file system family can deal with filenames in
55 The Microsoft FAT file system family can deal with filenames in
67 The Microsoft FAT file system family can deal with filenames in
80 The Microsoft FAT file system family can deal with filenames in
96 The Microsoft FAT file system family can deal with filenames in
111 The Microsoft FAT file system family can deal with filenames in
122 The Microsoft FAT file system family can deal with filenames in
133 The Microsoft FAT file system family can deal with filenames in
[all …]
/Linux-v5.4/Documentation/devicetree/bindings/misc/
Dallwinner,syscon.txt1 * Allwinner sun8i system controller
3 This file describes the bindings for the system controller present in
8 Required properties for the system controller:
11 "allwinner,sun8i-h3-system-controller"
12 "allwinner,sun8i-v3s-system-controller"
13 "allwinner,sun50i-a64-system-controller"
14 "allwinner,sun8i-a83t-system-controller"
18 compatible = "allwinner,sun8i-h3-system-controller", "syscon";
/Linux-v5.4/tools/power/x86/turbostat/
Dturbostat.855 …system summary plus the specified cpu-set. If cpu-set is the string "core", then the system summa…
66 \fB--quiet\fP Do not decode and print the system configuration header information.
81 \fB--Summary\fP limits output to a 1-line System Summary for each interval.
91 …system configuration dump (if --quiet is not used) is followed by statistics. The first row of th…
103 …of interrupts serviced by that CPU during the measurement interval. The system total line is the …
104 \fBSMI\fP The number of System Management Interrupts serviced CPU during the measurement interval.…
105 …system summary line shows the sum for all CPUs. These are C-state names as exported in /sys/devic…
106 …centage that Linux requested C1, C2, C3.... The system summary is the average of all CPUs in the …
117 …system summary is the sum of the package throttling time, and thus may be higher than 100% on a mu…
121 By default, turbostat dumps all possible information -- a system configuration header, followed by …
[all …]

12345678910>>...217