Searched full:system (Results 1 – 25 of 10119) sorted by relevance
12345678910>>...405
| /kernel/linux/linux-5.10/drivers/eisa/ |
| D | eisa.ids | 18 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 …]
|
| /kernel/linux/linux-6.6/drivers/eisa/ |
| D | eisa.ids | 18 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 …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 1 What: /sys/devices/system/cpu/
10 /sys/devices/system/cpu/cpuX/
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 …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 1 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 …]
|
| D | sysfs-devices-memory | 1 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
33 What: /sys/devices/system/memory/memoryX/phys_index
37 The file /sys/devices/system/memory/memoryX/phys_index
42 What: /sys/devices/system/memory/memoryX/state
46 The file /sys/devices/system/memory/memoryX/state
[all …]
|
| /kernel/linux/linux-5.10/include/asm-generic/ |
| D | syscall.h | 3 * 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 …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 5 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 …]
|
| D | suspend-flows.rst | 5 System Suspend Code Flows
12 At least one global system-wide transition needs to be carried out for the
13 system to get from the working state into one of the supported
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
19 For those sleep states, the transition from the working state of the system into
20 the target sleep state is referred to as *system suspend* too (in the majority
21 of cases, whether this means a transition or a sleep state of the system should
23 working state is referred to as *system resume*.
26 different sleep states of the system are quite similar, but there are some
45 The following steps are taken in order to transition the system from the working
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 5 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 …]
|
| D | suspend-flows.rst | 5 System Suspend Code Flows
12 At least one global system-wide transition needs to be carried out for the
13 system to get from the working state into one of the supported
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
19 For those sleep states, the transition from the working state of the system into
20 the target sleep state is referred to as *system suspend* too (in the majority
21 of cases, whether this means a transition or a sleep state of the system should
23 working state is referred to as *system resume*.
26 different sleep states of the system are quite similar, but there are some
45 The following steps are taken in order to transition the system from the working
[all …]
|
| /kernel/linux/linux-5.10/arch/powerpc/include/asm/ |
| D | ipic.h | 26 #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 …]
|
| /kernel/linux/linux-6.6/arch/powerpc/include/asm/ |
| D | ipic.h | 26 #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 …]
|
| /kernel/linux/linux-6.6/include/asm-generic/ |
| D | syscall.h | 3 * 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 * returned nonzero to prevent the system call from taking place.
[all …]
|
| /kernel/linux/linux-5.10/arch/nds32/include/asm/ |
| D | syscall.h | 14 * 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 …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | adding-syscalls.rst | 4 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 …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | adding-syscalls.rst | 4 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 …]
|
| /kernel/liteos_m/arch/risc-v/nuclei/gcc/nmsis/Core/Include/ |
| D | core_feature_timer.h | 22 * @brief System Timer feature API header file for Nuclei N/NX Core
25 * System Timer Feature Configuration Macro:
26 * 1. __SYSTIMER_PRESENT: Define whether Private System Timer is present or not.
29 * 2. __SYSTIMER_BASEADDR: Define the base address of the System Timer.
37 * \defgroup NMSIS_Core_SysTimer_Registers Register Define and Type Definitions Of System Timer
39 * \brief Type definitions and defines for system timer registers.
44 * \brief Structure type to access the System Timer (SysTimer).
46 * Structure definition to access the system timer(SysTimer).
53 …__IOM uint64_t MTIMER; /*!< Offset: 0x000 (R/W) System Timer current value 64bit…
54 …__IOM uint64_t MTIMERCMP; /*!< Offset: 0x008 (R/W) System Timer compare Value 64bit…
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/hisilicon/controller/ |
| D | sysctrl.yaml | 7 title: Hisilicon system controller
13 The Hisilicon system controller is used on many Hisilicon boards, it can be
14 used to assist the slave core startup, reboot the system, etc.
16 There are some variants of the Hisilicon system controller, such as HiP01,
17 Hi3519, Hi6220 system controller, each of them is mostly compatible with the
18 Hisilicon system controller, but some same registers located at different
19 offset. In addition, the HiP01 system controller has some specific control
22 The compatible names of each system controller are as follows:
23 Hisilicon system controller --> hisilicon,sysctrl
24 HiP01 system controller --> hisilicon,hip01-sysctrl
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/hisilicon/controller/ |
| D | sysctrl.yaml | 7 title: Hisilicon system controller
13 The Hisilicon system controller is used on many Hisilicon boards, it can be
14 used to assist the slave core startup, reboot the system, etc.
16 There are some variants of the Hisilicon system controller, such as HiP01,
17 Hi3519, Hi6220 system controller, each of them is mostly compatible with the
18 Hisilicon system controller, but some same registers located at different
19 offset. In addition, the HiP01 system controller has some specific control
22 The compatible names of each system controller are as follows:
23 Hisilicon system controller --> hisilicon,sysctrl
24 HiP01 system controller --> hisilicon,hip01-sysctrl
[all …]
|
| /kernel/linux/linux-5.10/Documentation/livepatch/ |
| D | system-state.rst | 2 System State Changes
5 Some users are really reluctant to reboot a system. This brings the need
14 change the system behavior or state so that it is no longer safe to
19 This is where the livepatch system state tracking gets useful. It
22 - store data needed to manipulate and restore the system state
28 1. Livepatch system state API
31 The state of the system might get modified either by several livepatch callbacks
46 - Non-zero number used to identify the affected system state.
50 - Number describing the variant of the system state change that
68 The system state version is used to prevent loading incompatible livepatches.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/livepatch/ |
| D | system-state.rst | 2 System State Changes
5 Some users are really reluctant to reboot a system. This brings the need
14 change the system behavior or state so that it is no longer safe to
19 This is where the livepatch system state tracking gets useful. It
22 - store data needed to manipulate and restore the system state
28 1. Livepatch system state API
31 The state of the system might get modified either by several livepatch callbacks
46 - Non-zero number used to identify the affected system state.
50 - Number describing the variant of the system state change that
68 The system state version is used to prevent loading incompatible livepatches.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 1 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 …]
|
| /kernel/uniproton/demos/raspi4/component/ |
| D | UniProton-patch-for-libmetal.patch | 34 diff -uparN libmetal-2022.10.0/lib/system/uniproton/alloc.h libmetal/lib/system/uniproton/alloc.h
35 --- libmetal-2022.10.0/lib/system/uniproton/alloc.h 1970-01-01 08:00:00.000000000 +0800
36 +++ libmetal/lib/system/uniproton/alloc.h 2023-02-20 14:53:22.000000000 +0800
77 diff -uparN libmetal-2022.10.0/lib/system/uniproton/assert.h libmetal/lib/system/uniproton/assert.h
78 --- libmetal-2022.10.0/lib/system/uniproton/assert.h 1970-01-01 08:00:00.000000000 +0800
79 +++ libmetal/lib/system/uniproton/assert.h 2022-12-26 10:59:44.000000000 +0800
107 diff -uparN libmetal-2022.10.0/lib/system/uniproton/cache.h libmetal/lib/system/uniproton/cache.h
108 --- libmetal-2022.10.0/lib/system/uniproton/cache.h 1970-01-01 08:00:00.000000000 +0800
109 +++ libmetal/lib/system/uniproton/cache.h 2022-12-26 11:02:08.000000000 +0800
150 diff -uparN libmetal-2022.10.0/lib/system/uniproton/CMakeLists.txt libmetal/lib/system/uniproton/CM…
[all …]
|
| /kernel/uniproton/demos/hi3093/component/ |
| D | UniProton-patch-for-libmetal.patch | 34 diff -uparN libmetal-2022.10.0/lib/system/uniproton/alloc.h libmetal/lib/system/uniproton/alloc.h
35 --- libmetal-2022.10.0/lib/system/uniproton/alloc.h 1970-01-01 08:00:00.000000000 +0800
36 +++ libmetal/lib/system/uniproton/alloc.h 2023-02-20 14:53:22.000000000 +0800
77 diff -uparN libmetal-2022.10.0/lib/system/uniproton/assert.h libmetal/lib/system/uniproton/assert.h
78 --- libmetal-2022.10.0/lib/system/uniproton/assert.h 1970-01-01 08:00:00.000000000 +0800
79 +++ libmetal/lib/system/uniproton/assert.h 2022-12-26 10:59:44.000000000 +0800
107 diff -uparN libmetal-2022.10.0/lib/system/uniproton/cache.h libmetal/lib/system/uniproton/cache.h
108 --- libmetal-2022.10.0/lib/system/uniproton/cache.h 1970-01-01 08:00:00.000000000 +0800
109 +++ libmetal/lib/system/uniproton/cache.h 2022-12-26 11:02:08.000000000 +0800
150 diff -uparN libmetal-2022.10.0/lib/system/uniproton/CMakeLists.txt libmetal/lib/system/uniproton/CM…
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 1 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 …]
|
12345678910>>...405