Home
last modified time | relevance | path

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

12345678910>>...86

/linux/Documentation/devicetree/bindings/arm/hisilicon/controller/
A Dsysctrl.yaml7 title: Hisilicon system controller
23 Hisilicon system controller --> hisilicon,sysctrl
68 description: offset in sysctrl for system reboot
94 /* Hisilicon system controller */
95 system-controller@802000 {
113 /* HiP01 system controller */
114 system-controller@10000000 {
120 /* Hi6220 system controller */
121 system-controller@f7030000 {
127 /* Hi3519 system controller */
[all …]
/linux/Documentation/ABI/testing/
A 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 …]
A 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
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
89 What: /sys/devices/system/memoryX/nodeY
[all …]
A 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.
78 What: /sys/devices/system/edac/mc/mc*/max_location
[all …]
/linux/Documentation/devicetree/bindings/sram/
A Dallwinner,sun4i-a10-system-control.yaml29 - const: allwinner,sun4i-a10-system-control
30 - const: allwinner,sun5i-a13-system-control
32 - const: allwinner,sun7i-a20-system-control
33 - const: allwinner,sun4i-a10-system-control
34 - const: allwinner,sun8i-a23-system-control
35 - const: allwinner,sun8i-h3-system-control
38 - const: allwinner,sun8i-h3-system-control
44 - const: allwinner,sun50i-a64-system-control
45 - const: allwinner,sun50i-h5-system-control
52 - const: allwinner,sun50i-h616-system-control
[all …]
/linux/tools/testing/selftests/bpf/
A Dtest_dev_cgroup.c57 assert(system("rm -f /tmp/test_dev_cgroup_null") == 0); in main()
58 assert(system("mknod /tmp/test_dev_cgroup_null c 1 3")); in main()
59 assert(system("rm -f /tmp/test_dev_cgroup_null") == 0); in main()
62 assert(system("rm -f /tmp/test_dev_cgroup_zero") == 0); in main()
63 assert(system("mknod /tmp/test_dev_cgroup_zero c 1 5") == 0); in main()
64 assert(system("rm -f /tmp/test_dev_cgroup_zero") == 0); in main()
66 assert(system("dd if=/dev/urandom of=/dev/zero count=64") == 0); in main()
69 assert(system("dd if=/dev/urandom of=/dev/full count=64")); in main()
72 assert(system("dd if=/dev/random of=/dev/zero count=64")); in main()
/linux/Documentation/admin-guide/pm/
A Dsleep-states.rst36 states while the system is suspended.
54 operating state is lost (the system core logic retains power), so the system can
71 the S1 system state defined by ACPI.
118 It takes three system state changes to put it into hibernation and two system
157 interface for system sleep regardless of the underlying system architecture or
210 mechanism to put the system to sleep after creating a
215 Power off the system.
218 Reboot the system (useful for diagnostics mostly).
221 Hybrid system suspend. Put the system into the suspend sleep
225 to restore the previous state of the system.
[all …]
A 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 …]
A Dsuspend-flows.rst16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
48 1. Invoking system-wide suspend notifiers.
115 system wakeup, in which case the system resume transition is started.
135 the system resume transition begins.
157 4. Invoking system-wide resume notifiers.
170 1. Invoking system-wide suspend notifiers.
198 configuration of system wakeup sources usually starts when system wakeup
218 5. Suspending core system components.
239 1. Platform-specific system wakeup.
247 2. Resuming core system components.
[all …]
/linux/Documentation/ABI/stable/
A 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
71 in the system.
[all …]
A 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
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
74 What: /sys/devices/system/cpu/cpuX/topology/package_cpus
[all …]
/linux/Documentation/livepatch/
A 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
71 - Any completely new system state modification is allowed.
74 for already modified system states.
80 system states.
123 when the entire system is able to handle it.
133 - Do the actual system state modification. Eventually allow
[all …]
/linux/Documentation/process/
A 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
63 together with the corresponding follow-up system calls --
72 flags, and reject the system call (with ``EINVAL``) if it does::
202 number of arguments to the system call, and the macro takes the system call name
226 system call, returning ``-ENOSYS``. Add your new system call here too::
393 For most system calls, once the system call is complete the user program
405 control of where and how execution continues after the system call.
453 new system call, it's worth doing a kernel-wide grep for the existing system
[all …]
/linux/tools/testing/selftests/bpf/prog_tests/
A Dxdp_bonding.c148 if (!ASSERT_OK(system(cmd), cmd)) \ in bonding_setup()
208 ASSERT_OK(system("ip link delete bond1"), "delete bond1"); in bonding_cleanup()
406 err = system("ip link set veth master bond"); in test_xdp_bonding_attach()
444 err = system("ip link set vxlan master bond"); in test_xdp_bonding_attach()
457 system("ip link del veth"); in test_xdp_bonding_attach()
458 system("ip link del bond"); in test_xdp_bonding_attach()
459 system("ip link del vxlan"); in test_xdp_bonding_attach()
478 err = system("ip link set bond_nest1 master bond"); in test_xdp_bonding_nested()
494 system("ip link del bond"); in test_xdp_bonding_nested()
495 system("ip link del bond_nest1"); in test_xdp_bonding_nested()
[all …]
/linux/drivers/media/rc/
A 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()
221 system = (scancode & 0x1f00) >> 8; in ir_rc5_encode()
[all …]
/linux/Documentation/admin-guide/
A 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
52 The generic error record provides enough information for a file system
[all …]
A Dinitrd.rst38 6) init mounts the "real" root file system
40 pivot_root system call
43 9) the initrd file system is removed
100 "normal" root file system, e.g.::
120 system) must be compiled into the kernel.
140 3) mount the file system, e.g.::
164 7) unmount the file system::
217 - mounting the new root file system
218 - turning it into the root file system
289 have to be a very usable system yet)
[all …]
/linux/fs/minix/
A DKconfig3 tristate "Minix file system support"
6 Minix is a simple operating system used in many classes about OS's.
7 The minix file system (method to organize files on a hard disk
8 partition or a floppy disk) was the original file system for Linux,
9 but has been superseded by the second extended file system ext2fs.
10 You don't want to use the minix file system on your hard disk
15 To compile this file system support as a module, choose M here: the
16 module will be called minix. Note that the file system of your root
/linux/Documentation/admin-guide/mm/
A Dnumaperf.rst47 # symlinks -v /sys/devices/system/node/nodeX/access0/targets/
74 /sys/devices/system/node/nodeY/access0/initiators/
83 /sys/devices/system/node/nodeY/access0/initiators/
114 cache provided by the system.
123 software accesses a system address, the system will return it from the
138 /sys/devices/system/node/nodeX/memory_side_cache/
146 /sys/devices/system/node/nodeX/memory_side_cache/indexA/
147 /sys/devices/system/node/nodeX/memory_side_cache/indexB/
148 /sys/devices/system/node/nodeX/memory_side_cache/indexC/
154 # tree /sys/devices/system/node/node0/memory_side_cache/
[all …]
/linux/kernel/trace/
A Dtrace_events.c916 kfree(system); in __put_system()
1427 if (system && strcmp(call->class->system, system->name) != 0) in system_enable_read()
1478 if (system) in system_enable_write()
1735 if (!system) in subsystem_open()
2234 system = kmalloc(sizeof(*system), GFP_KERNEL); in create_new_subsystem()
2235 if (!system) in create_new_subsystem()
2253 return system; in create_new_subsystem()
2257 kfree(system); in create_new_subsystem()
2294 if (!system) in event_subsystem_dir()
2664 if (call->class->system == map[i]->system) { in trace_event_eval_update()
[all …]
/linux/Documentation/devicetree/bindings/arm/marvell/
A 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/Documentation/crypto/
A Duserspace-if.rst63 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
124 - MSG_MORE: If this flag is set, the send system call acts like a
165 send/recv system call family. That cmsghdr data structure holds the
178 - MSG_MORE: If this flag is set, the send system call acts like a
180 subsequent invocation of the send system call.
241 - MSG_MORE: If this flag is set, the send system call acts like a
243 subsequent invocation of the send system call.
[all …]
/linux/Documentation/power/
A Dsuspend-and-interrupts.rst12 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
67 during system sleep so as to trigger a system wakeup when needed. For example,
83 re-enabled by resume_device_irqs() during the subsequent system resume. Also
84 the PM core is notified about the event which causes the system suspend in
89 system suspend currently in progress to be aborted or wake up the system if
92 IRQs at that time, but those IRQs should not be configured for system wakeup
105 IRQ subsystem to trigger a system wakeup.
[all …]
/linux/Documentation/devicetree/bindings/power/
A 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/fs/nilfs2/
A DKconfig3 tristate "NILFS2 file system support"
6 NILFS2 is a log-structured file system (LFS) supporting continuous
8 file system, users can even restore files mistakenly overwritten or
9 destroyed just a few seconds ago. Since this file system can keep
11 system crashes.
18 snapshot is mountable as a read-only file system concurrently with
24 To compile this file system support as a module, choose M here: the

Completed in 55 milliseconds

12345678910>>...86