Home
last modified time | relevance | path

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

12345678910>>...75

/linux/Documentation/ABI/testing/
H 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 …]
H 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
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 …]
H 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.
56 What: /sys/devices/system/edac/mc/mc*/ce_noinfo_count
[all …]
/linux/tools/tracing/rtla/src/
H A Dtrace.c266 free(free_event->system); in trace_events_free()
282 tevent->system = strdup(event_string); in trace_event_alloc()
283 if (!tevent->system) { in trace_event_alloc()
288 tevent->event = strstr(tevent->system, ":"); in trace_event_alloc()
342 debug_msg("Disabling %s:%s filter %s\n", tevent->system, in trace_event_disable_filter()
347 retval = tracefs_event_file_write(instance->inst, tevent->system, in trace_event_disable_filter()
350 err_msg("Error disabling %s:%s filter %s\n", tevent->system, in trace_event_disable_filter()
379 snprintf(path, 1024, "%s_%s_hist.txt", tevent->system, tevent->event); in trace_event_save_hist()
381 printf(" Saving event %s:%s hist to %s\n", tevent->system, tevent->event, path); in trace_event_save_hist()
389 hist = tracefs_event_file_read(instance->inst, tevent->system, tevent->event, "hist", 0); in trace_event_save_hist()
[all …]
/linux/tools/testing/selftests/bpf/prog_tests/
H A 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/Documentation/admin-guide/pm/
H A 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 …]
H 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 …]
H A 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/Documentation/livepatch/
H 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
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/Documentation/process/
H 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
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/drivers/media/rc/
H 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()
214 unsigned int data, xdata, command, commandx, system, pre_space_data; in ir_rc5_encode() local
[all …]
/linux/Documentation/admin-guide/
H 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
33 At the time of this writing, the only file system that emits FAN_FS_ERROR
[all …]
H A 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 …]
H A Dworkload-tracing.rst14 * Understanding system resources necessary to build and run a workload
16 * Linux tracing and strace can be used to discover the system resources
17 in use by a workload. The completeness of the system usage information
19 * Performance and security of the operating system can be analyzed with
32 the system resources in use by a workload. Once we discover and understand
36 This method of tracing using strace tells us the system calls invoked by
37 the workload and doesn't include all the system calls that can be invoked
39 these system calls that are invoked. As an example, if a workload opens a
41 is traced. Any error paths in that system call will not be traced. If there
44 of the system usage information depends on the completeness of coverage of a
[all …]
/linux/Documentation/devicetree/bindings/arm/marvell/
H 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/fs/minix/
H A 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/kernel/trace/
H A Dtrace_events.c56 static inline int system_refcount(struct event_subsystem *system) in system_refcount() argument
58 return system->ref_count; in system_refcount()
61 static int system_refcount_inc(struct event_subsystem *system) in system_refcount_inc() argument
63 return system->ref_count++; in system_refcount_inc()
66 static int system_refcount_dec(struct event_subsystem *system) in system_refcount_dec() argument
68 return --system->ref_count; in system_refcount_dec()
900 char *system;
909 kfree(event_mod->system); in free_event_mod()
924 const char *match, const char *system, const char *event) in remove_cache_mod()
936 if (system in remove_cache_mod()
898 char *system; global() member
922 remove_cache_mod(struct trace_array * tr,const char * mod,const char * match,const char * system,const char * event) remove_cache_mod() argument
950 cache_mod(struct trace_array * tr,const char * mod,int set,const char * match,const char * system,const char * event) cache_mod() argument
1001 cache_mod(struct trace_array * tr,const char * mod,int set,const char * match,const char * system,const char * event) cache_mod() argument
1207 __put_system(struct event_subsystem * system) __put_system() argument
1225 __get_system(struct event_subsystem * system) __get_system() argument
1454 trace_set_clr_event(const char * system,const char * event,int set) trace_set_clr_event() argument
1478 trace_array_set_clr_event(struct trace_array * tr,const char * system,const char * event,bool enable) trace_array_set_clr_event() argument
1668 const char *system; s_show() local
1847 trace_events_enabled(struct trace_array * tr,const char * system) trace_events_enabled() argument
1887 struct event_subsystem *system = dir->subsystem; system_enable_read() local
1908 struct event_subsystem *system = dir->subsystem; system_enable_write() local
2175 struct event_subsystem *system = NULL; subsystem_open() local
2266 struct event_subsystem *system = dir->subsystem; subsystem_filter_read() local
2727 struct event_subsystem *system; create_new_subsystem() local
2775 struct event_subsystem *system, *iter; event_subsystem_dir() local
3450 const char *system; event_in_systems() local
3853 __find_event_file(struct trace_array * tr,const char * system,const char * event) __find_event_file() argument
3876 find_event_file(struct trace_array * tr,const char * system,const char * event) find_event_file() argument
3909 trace_get_event_file(const char * instance,const char * system,const char * event) trace_get_event_file() argument
4159 const char *system; event_enable_func() local
4715 struct event_subsystem *system; event_trace_self_tests() local
[all...]
/linux/Documentation/admin-guide/mm/
H A 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/tools/testing/selftests/lkdtm/
H A Dtests.txt2 #PANIC_STOP_IRQOFF Crashes entire system
3 #PANIC_IN_HARDIRQ Crashes entire system
5 #BUG_IN_HARDIRQ Crashes entire system
9 #LOOP Hangs the system
11 #CORRUPT_STACK Crashes entire system on success
12 #CORRUPT_STACK_STRONG Crashes entire system on success
34 #SOFTLOCKUP Hangs the system
35 #HARDLOCKUP Hangs the system
36 #SMP_CALL_LOCKUP Hangs the system
37 #SPINLOCKUP Hangs the system
[all...]
/linux/tools/testing/selftests/cpu-hotplug/
H A 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/include/trace/
H A 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/Documentation/devicetree/bindings/power/
H 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/
H A 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
/linux/Documentation/power/
H 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
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 states, the corresponding input of that interrupt
77 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
83 re-enabled by resume_device_irqs() during the subsequent system resume. Also
[all …]
/linux/Documentation/ABI/stable/
H A 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

12345678910>>...75