Home
last modified time | relevance | path

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

12345678910>>...83

/Linux-v4.19/tools/testing/selftests/bpf/
Dtest_dev_cgroup.c71 assert(system("rm -f /tmp/test_dev_cgroup_null") == 0); in main()
72 assert(system("mknod /tmp/test_dev_cgroup_null c 1 3")); in main()
73 assert(system("rm -f /tmp/test_dev_cgroup_null") == 0); in main()
76 assert(system("rm -f /tmp/test_dev_cgroup_zero") == 0); in main()
77 assert(system("mknod /tmp/test_dev_cgroup_zero c 1 5") == 0); in main()
78 assert(system("rm -f /tmp/test_dev_cgroup_zero") == 0); in main()
80 assert(system("dd if=/dev/urandom of=/dev/zero count=64") == 0); in main()
83 assert(system("dd if=/dev/urandom of=/dev/full count=64")); in main()
86 assert(system("dd if=/dev/random of=/dev/zero count=64")); in main()
Dtest_cgroup_storage.c85 assert(system("ping localhost -c 1 -W 1 -q > /dev/null") == 0); in main()
86 assert(system("ping localhost -c 1 -W 1 -q > /dev/null")); in main()
87 assert(system("ping localhost -c 1 -W 1 -q > /dev/null") == 0); in main()
108 assert(system("ping localhost -c 1 -W 1 -q > /dev/null") == 0); in main()
109 assert(system("ping localhost -c 1 -W 1 -q > /dev/null")); in main()
110 assert(system("ping localhost -c 1 -W 1 -q > /dev/null") == 0); in main()
/Linux-v4.19/Documentation/ABI/testing/
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-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-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-v4.19/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-v4.19/Documentation/admin-guide/pm/
Dstrategies.rst11 One of them is based on using global low-power states of the whole system in
12 which user space code cannot be executed and the overall system activity is
14 kernel puts the system into one of these states when requested by user space
15 and the system stays in it until a special signal is received from one of
17 user space code can run. Because sleep states are global and the whole system
19 :doc:`system-wide power management <system-wide>`.
23 components of the system, as needed, in the working state. In consequence, if
24 this strategy is in use, the working state of the system usually does not
26 a metastate covering a range of different power states of the system in which
33 If all of the system components are active, the system as a whole is regarded as
[all …]
Dsleep-states.rst9 Sleep states are global low-power states of the entire system in which user
10 space code cannot be executed and the overall system activity is significantly
18 the Linux kernel can support up to four system sleep states, including
19 hibernation and up to three variants of system suspend. The sleep states that
27 This is a generic, pure software, light-weight variant of system suspend (also
32 states while the system is suspended.
34 The system is woken up from this state by in-band interrupts, so theoretically
40 deeper system suspend variants to provide reduced resume latency. It is always
50 operating state is lost (the system core logic retains power), so the system can
55 <s2idle>` too, nonboot CPUs are taken offline and all low-level system functions
[all …]
/Linux-v4.19/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-xen_memory1 What: /sys/devices/system/xen_memory/xen_memory0/max_retry_count
11 What: /sys/devices/system/xen_memory/xen_memory0/max_schedule_delay
19 What: /sys/devices/system/xen_memory/xen_memory0/retry_count
30 What: /sys/devices/system/xen_memory/xen_memory0/schedule_delay
41 What: /sys/devices/system/xen_memory/xen_memory0/target
49 What: /sys/devices/system/xen_memory/xen_memory0/target_kb
56 What: /sys/devices/system/xen_memory/xen_memory0/info/current_kb
64 What: /sys/devices/system/xen_memory/xen_memory0/info/high_kb
71 What: /sys/devices/system/xen_memory/xen_memory0/info/low_kb
79 What: /sys/devices/system/xen_memory/xen_memory0/scrub_pages
/Linux-v4.19/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-v4.19/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-v4.19/fs/minix/
DKconfig2 tristate "Minix file system support"
5 Minix is a simple operating system used in many classes about OS's.
6 The minix file system (method to organize files on a hard disk
7 partition or a floppy disk) was the original file system for Linux,
8 but has been superseded by the second extended file system ext2fs.
9 You don't want to use the minix file system on your hard disk
14 To compile this file system support as a module, choose M here: the
15 module will be called minix. Note that the file system of your root
/Linux-v4.19/Documentation/process/
Dadding-syscalls.rst4 This document describes what's involved in adding a new system call to the
12 The first thing to consider when adding a new system call is whether one of
13 the alternatives might be suitable instead. Although system calls are the
32 - If you're just exposing runtime system information, a new node in sysfs
40 :manpage:`fcntl(2)` is a multiplexing system call that hides a lot of complexity, so
46 with :manpage:`fcntl(2)`, this system call is a complicated multiplexor so
54 A new system call forms part of the API of the kernel, and has to be supported
60 together with the corresponding follow-up system calls --
65 For simpler system calls that only take a couple of arguments, the preferred
67 system call. To make sure that userspace programs can safely use flags
[all …]
/Linux-v4.19/kernel/trace/
Dtrace_events.c45 static inline int system_refcount(struct event_subsystem *system) in system_refcount() argument
47 return system->ref_count; in system_refcount()
50 static int system_refcount_inc(struct event_subsystem *system) in system_refcount_inc() argument
52 return system->ref_count++; in system_refcount_inc()
55 static int system_refcount_dec(struct event_subsystem *system) in system_refcount_dec() argument
57 return --system->ref_count; in system_refcount_dec()
652 static void __put_system(struct event_subsystem *system) in __put_system() argument
654 struct event_filter *filter = system->filter; in __put_system()
656 WARN_ON_ONCE(system_refcount(system) == 0); in __put_system()
657 if (system_refcount_dec(system)) in __put_system()
[all …]
/Linux-v4.19/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
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
37 other system hardening techniques and, potentially, an LSM of your
[all …]
/Linux-v4.19/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-v4.19/fs/nilfs2/
DKconfig2 tristate "NILFS2 file system support"
5 NILFS2 is a log-structured file system (LFS) supporting continuous
7 file system, users can even restore files mistakenly overwritten or
8 destroyed just a few seconds ago. Since this file system can keep
10 system crashes.
17 snapshot is mountable as a read-only file system concurrently with
23 To compile this file system support as a module, choose M here: the
/Linux-v4.19/Documentation/devicetree/bindings/arm/hisilicon/
Dhisilicon.txt51 Hisilicon system controller
64 - reboot-offset : offset in sysctrl for system reboot
69 sysctrl: system-controller@fc802000 {
101 Hisilicon Hi6220 system controller
109 Hisilicon designs this controller as one of the system controllers,
110 its main functions are the same as Hisilicon system controller, but
130 Hisilicon designs this system controller to control the power always
150 Hisilicon designs this system controller to control the multimedia
170 Hisilicon designs this system controller to control the power management
200 Hisilicon HiP01 system controller
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/pinctrl/
Dberlin,pinctrl.txt3 Pin control registers are part of both chip controller and system
5 either the chip controller or system controller node. The pins
19 "marvell,berlin2-system-pinctrl",
21 "marvell,berlin2cd-system-pinctrl",
23 "marvell,berlin2q-system-pinctrl",
26 "marvell,berlin4ct-system-pinctrl",
36 compatible = "marvell,berlin2q-system-pinctrl";
/Linux-v4.19/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-v4.19/Documentation/
Dcputopology.txt8 1) /sys/devices/system/cpu/cpuX/topology/physical_package_id:
14 2) /sys/devices/system/cpu/cpuX/topology/core_id:
20 3) /sys/devices/system/cpu/cpuX/topology/book_id:
26 4) /sys/devices/system/cpu/cpuX/topology/drawer_id:
32 5) /sys/devices/system/cpu/cpuX/topology/thread_siblings:
37 6) /sys/devices/system/cpu/cpuX/topology/thread_siblings_list:
42 7) /sys/devices/system/cpu/cpuX/topology/core_siblings:
47 8) /sys/devices/system/cpu/cpuX/topology/core_siblings_list:
52 9) /sys/devices/system/cpu/cpuX/topology/book_siblings:
57 10) /sys/devices/system/cpu/cpuX/topology/book_siblings_list:
[all …]
/Linux-v4.19/Documentation/devicetree/bindings/arm/uniphier/
Dcache-uniphier.txt3 UniPhier SoCs are integrated with a full-custom outer cache controller system.
8 - compatible: should be "socionext,uniphier-system-cache"
21 cache should be also compatible with "socionext,uniphier-system-cache".
26 Example 1 (system with L2):
28 compatible = "socionext,uniphier-system-cache";
38 Example 2 (system with L2 and L3):
40 compatible = "socionext,uniphier-system-cache";
52 compatible = "socionext,uniphier-system-cache";
/Linux-v4.19/Documentation/power/
Dsuspend-and-interrupts.txt10 Device interrupt request lines (IRQs) are generally disabled during system
27 Device IRQs are re-enabled during system resume, right before the "early" phase
35 There are interrupts that can legitimately trigger during the entire system
45 interrupt will wake the system from a suspended state -- for such cases it is
59 System wakeup interrupts generally need to be configured to wake up the system
65 during system sleep so as to trigger a system wakeup when needed. For example,
67 handling system wakeup events. Then, if a given interrupt line is supposed to
68 wake up the system from sleep sates, the corresponding input of that interrupt
75 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
81 re-enabled by resume_device_irqs() during the subsequent system resume. Also
[all …]
/Linux-v4.19/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 …]

12345678910>>...83