Home
last modified time | relevance | path

Searched refs:system (Results 1 – 25 of 2865) sorted by relevance

12345678910>>...115

/linux-6.6.21/Documentation/devicetree/bindings/arm/hisilicon/controller/
Dsysctrl.yaml7 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 …]
/linux-6.6.21/tools/tracing/rtla/src/
Dtrace.c216 free(free_event->system); in trace_events_free()
232 tevent->system = strdup(event_string); in trace_event_alloc()
233 if (!tevent->system) { in trace_event_alloc()
238 tevent->event = strstr(tevent->system, ":"); in trace_event_alloc()
292 debug_msg("Disabling %s:%s filter %s\n", tevent->system, in trace_event_disable_filter()
297 retval = tracefs_event_file_write(instance->inst, tevent->system, in trace_event_disable_filter()
300 err_msg("Error disabling %s:%s filter %s\n", tevent->system, in trace_event_disable_filter()
329 snprintf(path, 1024, "%s_%s_hist.txt", tevent->system, tevent->event); in trace_event_save_hist()
331 printf(" Saving event %s:%s hist to %s\n", tevent->system, tevent->event, path); in trace_event_save_hist()
339 hist = tracefs_event_file_read(instance->inst, tevent->system, tevent->event, "hist", 0); in trace_event_save_hist()
[all …]
/linux-6.6.21/Documentation/devicetree/bindings/sram/
Dallwinner,sun4i-a10-system-control.yaml4 $id: http://devicetree.org/schemas/sram/allwinner,sun4i-a10-system-control.yaml#
32 - allwinner,sun4i-a10-system-control
33 - allwinner,sun5i-a13-system-control
34 - allwinner,sun8i-a23-system-control
35 - allwinner,sun8i-h3-system-control
36 - allwinner,sun20i-d1-system-control
37 - allwinner,sun50i-a64-system-control
38 - allwinner,sun50i-h5-system-control
39 - allwinner,sun50i-h616-system-control
42 - allwinner,suniv-f1c100s-system-control
[all …]
/linux-6.6.21/tools/testing/selftests/bpf/
Dtest_dev_cgroup.c60 assert(system("rm -f /tmp/test_dev_cgroup_null") == 0); in main()
61 assert(system("mknod /tmp/test_dev_cgroup_null c 1 3")); in main()
62 assert(system("rm -f /tmp/test_dev_cgroup_null") == 0); in main()
65 assert(system("rm -f /tmp/test_dev_cgroup_zero") == 0); in main()
66 assert(system("mknod /tmp/test_dev_cgroup_zero c 1 5") == 0); in main()
67 assert(system("rm -f /tmp/test_dev_cgroup_zero") == 0); in main()
69 assert(system("dd if=/dev/urandom of=/dev/zero count=64") == 0); in main()
72 assert(system("dd if=/dev/urandom of=/dev/full count=64")); in main()
75 assert(system("dd if=/dev/random of=/dev/zero count=64")); in main()
/linux-6.6.21/Documentation/ABI/testing/
Dsysfs-devices-system-cpu1 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 …]
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 is a
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 …]
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 …]
/linux-6.6.21/tools/testing/selftests/bpf/prog_tests/
Dxdp_bonding.c201 ASSERT_OK(system("ip link delete bond1"), "delete bond1"); in bonding_cleanup()
202 ASSERT_OK(system("ip link delete veth1_1"), "delete veth1_1"); in bonding_cleanup()
203 ASSERT_OK(system("ip link delete veth1_2"), "delete veth1_2"); in bonding_cleanup()
204 ASSERT_OK(system("ip netns delete ns_dst"), "delete ns_dst"); in bonding_cleanup()
386 if (!ASSERT_OK(system("ip link add veth type veth"), "add veth")) in test_xdp_bonding_attach()
388 if (!ASSERT_OK(system("ip link add bond type bond"), "add bond")) in test_xdp_bonding_attach()
403 err = system("ip link set veth master bond"); in test_xdp_bonding_attach()
437 if (!ASSERT_OK(system("ip link add vxlan type vxlan id 1 remote 1.2.3.4 dstport 0 dev lo"), in test_xdp_bonding_attach()
441 err = system("ip link set vxlan master bond"); in test_xdp_bonding_attach()
454 system("ip link del veth"); in test_xdp_bonding_attach()
[all …]
/linux-6.6.21/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 …]
Dsysfs-devices-system-cpu1 What: /sys/devices/system/cpu/dscr_default
6 /sys/devices/system/cpu/cpuN/dscr on all CPUs.
12 What: /sys/devices/system/cpu/cpu[0-9]+/dscr
27 What: /sys/devices/system/cpu/cpuX/topology/physical_package_id
33 What: /sys/devices/system/cpu/cpuX/topology/die_id
39 What: /sys/devices/system/cpu/cpuX/topology/core_id
45 What: /sys/devices/system/cpu/cpuX/topology/cluster_id
51 What: /sys/devices/system/cpu/cpuX/topology/book_id
57 What: /sys/devices/system/cpu/cpuX/topology/drawer_id
63 What: /sys/devices/system/cpu/cpuX/topology/core_cpus
[all …]
/linux-6.6.21/Documentation/admin-guide/pm/
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 …]
Dsleep-states.rst13 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
59 <s2idle>` too, nonboot CPUs are taken offline and all low-level system functions
[all …]
Dsuspend-flows.rst12 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
48 1. Invoking system-wide suspend notifiers.
[all …]
/linux-6.6.21/Documentation/livepatch/
Dsystem-state.rst5 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.
71 - Any completely new system state modification is allowed.
[all …]
/linux-6.6.21/drivers/media/rc/
Dir-rc5-decoder.c114 u8 xdata, command, system; in ir_rc5_decode() local
121 system = (data->bits & 0x1F000) >> 12; in ir_rc5_decode()
124 scancode = system << 16 | command << 8 | xdata; in ir_rc5_decode()
129 u8 command, system; in ir_rc5_decode() local
135 system = (data->bits & 0x007C0) >> 6; in ir_rc5_decode()
138 scancode = system << 8 | command; in ir_rc5_decode()
143 u8 command, system; in ir_rc5_decode() local
149 system = (data->bits & 0x02FC0) >> 6; in ir_rc5_decode()
151 scancode = system << 6 | command; in ir_rc5_decode()
214 unsigned int data, xdata, command, commandx, system, pre_space_data; in ir_rc5_encode() local
[all …]
/linux-6.6.21/Documentation/process/
Dadding-syscalls.rst7 This document describes what's involved in adding a new system call to the
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 --
68 For simpler system calls that only take a couple of arguments, the preferred
70 system call. To make sure that userspace programs can safely use flags
[all …]
/linux-6.6.21/Documentation/devicetree/bindings/arm/marvell/
Dmvebu-system-controller.txt8 - "marvell,orion-system-controller"
9 - "marvell,armada-370-xp-system-controller"
10 - "marvell,armada-375-system-controller"
11 - reg: Should contain system controller registers location and length.
15 system-controller@d0018200 {
16 compatible = "marvell,armada-370-xp-system-controller";
/linux-6.6.21/Documentation/admin-guide/
Dfilesystem-monitoring.rst4 File system Monitoring with fanotify
7 File system Error Reporting
10 Fanotify supports the FAN_FS_ERROR event type for file system-wide error
11 reporting. It is meant to be used by file system health monitoring
13 sysadmin, start recovery) when a file system problem is detected.
16 for a monitoring tool to know a problem in the file system has happened.
20 early file system problem detection and reporting recovery tools.
22 When a file system operation fails, it is common for dozens of kernel
26 error that occurred for a file system since the last notification, and
33 At the time of this writing, the only file system that emits FAN_FS_ERROR
[all …]
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-6.6.21/include/trace/
Ddefine_custom_trace.h41 # define __TRACE_INCLUDE(system) <trace/events/system.h> argument
44 # define __TRACE_INCLUDE(system) __stringify(TRACE_INCLUDE_PATH/system.h) argument
47 # define TRACE_INCLUDE(system) __TRACE_INCLUDE(system) argument
/linux-6.6.21/fs/minix/
DKconfig3 tristate "Minix file system support"
7 Minix is a simple operating system used in many classes about OS's.
8 The minix file system (method to organize files on a hard disk
9 partition or a floppy disk) was the original file system for Linux,
10 but has been superseded by the second extended file system ext2fs.
11 You don't want to use the minix file system on your hard disk
16 To compile this file system support as a module, choose M here: the
17 module will be called minix. Note that the file system of your root
/linux-6.6.21/tools/testing/selftests/cpu-hotplug/
Dcpu-on-off-test.sh27 if ! ls $SYSFS/devices/system/cpu/cpu* > /dev/null 2>&1; then
33 online_cpus=`cat $SYSFS/devices/system/cpu/online`
41 present_cpus=`cat $SYSFS/devices/system/cpu/present`
47 offline_cpus=`cat $SYSFS/devices/system/cpu/offline`
63 for cpu in $SYSFS/devices/system/cpu/cpu*; do
82 grep -q 1 $SYSFS/devices/system/cpu/cpu$1/online
87 grep -q 0 $SYSFS/devices/system/cpu/cpu$1/online
92 echo 1 > $SYSFS/devices/system/cpu/cpu$1/online
97 echo 0 > $SYSFS/devices/system/cpu/cpu$1/online
/linux-6.6.21/Documentation/admin-guide/mm/
Dnumaperf.rst13 A system supports such heterogeneous memory by grouping each memory type
48 # symlinks -v /sys/devices/system/node/nodeX/access0/targets/
49 relative: /sys/devices/system/node/nodeX/access0/targets/nodeY -> ../../nodeY
51 # symlinks -v /sys/devices/system/node/nodeY/access0/initiators/
52 relative: /sys/devices/system/node/nodeY/access0/initiators/nodeX -> ../../nodeX
70 the system provides these attributes, the kernel exports them under the
74 /sys/devices/system/node/nodeY/access0/initiators/
82 # tree -P "read*|write*" /sys/devices/system/node/nodeY/access0/initiators/
83 /sys/devices/system/node/nodeY/access0/initiators/
105 system physical addresses memory initiators are aware of are provided
[all …]
/linux-6.6.21/Documentation/devicetree/bindings/power/
Dpower-controller.txt1 * Generic system power control capability
4 sometimes able to control the system power. The device driver associated with these
6 it can be used to switch off the system. The corresponding device must have the
7 standard property "system-power-controller" in its device node. This property
8 marks the device as able to control the system power. In order to test if this
16 system-power-controller;
/linux-6.6.21/fs/nilfs2/
DKconfig3 tristate "NILFS2 file system support"
8 NILFS2 is a log-structured file system (LFS) supporting continuous
10 file system, users can even restore files mistakenly overwritten or
11 destroyed just a few seconds ago. Since this file system can keep
13 system crashes.
20 snapshot is mountable as a read-only file system concurrently with
26 To compile this file system support as a module, choose M here: the

12345678910>>...115