Lines Matching +full:cpu +full:- +full:nr
13 ------------------------------------------------------------------------------
27 - acct
28 - acpi_video_flags
29 - auto_msgmni
30 - bootloader_type [ X86 only ]
31 - bootloader_version [ X86 only ]
32 - cap_last_cap
33 - core_pattern
34 - core_pipe_limit
35 - core_uses_pid
36 - ctrl-alt-del
37 - dmesg_restrict
38 - domainname
39 - hostname
40 - hotplug
41 - hardlockup_all_cpu_backtrace
42 - hardlockup_panic
43 - hung_task_panic
44 - hung_task_check_count
45 - hung_task_timeout_secs
46 - hung_task_check_interval_secs
47 - hung_task_warnings
48 - hyperv_record_panic_msg
49 - kexec_load_disabled
50 - kptr_restrict
51 - l2cr [ PPC only ]
52 - modprobe ==> Documentation/debugging-modules.txt
53 - modules_disabled
54 - msg_next_id [ sysv ipc ]
55 - msgmax
56 - msgmnb
57 - msgmni
58 - nmi_watchdog
59 - osrelease
60 - ostype
61 - overflowgid
62 - overflowuid
63 - panic
64 - panic_on_oops
65 - panic_on_stackoverflow
66 - panic_on_unrecovered_nmi
67 - panic_on_warn
68 - panic_print
69 - panic_on_rcu_stall
70 - perf_cpu_time_max_percent
71 - perf_event_paranoid
72 - perf_event_max_stack
73 - perf_event_mlock_kb
74 - perf_event_max_contexts_per_stack
75 - pid_max
76 - powersave-nap [ PPC only ]
77 - printk
78 - printk_delay
79 - printk_ratelimit
80 - printk_ratelimit_burst
81 - pty ==> Documentation/filesystems/devpts.txt
82 - randomize_va_space
83 - real-root-dev ==> Documentation/admin-guide/initrd.rst
84 - reboot-cmd [ SPARC only ]
85 - rtsig-max
86 - rtsig-nr
87 - sched_energy_aware
88 - seccomp/ ==> Documentation/userspace-api/seccomp_filter.rst
89 - sem
90 - sem_next_id [ sysv ipc ]
91 - sg-big-buff [ generic SCSI device (sg) ]
92 - shm_next_id [ sysv ipc ]
93 - shm_rmid_forced
94 - shmall
95 - shmmax [ sysv ipc ]
96 - shmmni
97 - softlockup_all_cpu_backtrace
98 - soft_watchdog
99 - stack_erasing
100 - stop-a [ SPARC only ]
101 - sysrq ==> Documentation/admin-guide/sysrq.rst
102 - sysctl_writes_strict
103 - tainted ==> Documentation/admin-guide/tainted-kernels.rst
104 - threads-max
105 - unknown_nmi_panic
106 - watchdog
107 - watchdog_thresh
108 - version
116 If BSD-style process accounting is enabled these values control
256 ctrl-alt-del:
259 When the value in this file is 0, ctrl-alt-del is trapped and
267 mode, the ctrl-alt-del is intercepted by the program before it
313 debug information. If enabled, arch-specific all-CPU stack dumping
327 0 - don't panic on hard lockup
328 1 - panic on hard lockup
330 See Documentation/admin-guide/lockup-watchdogs.rst for more information. This can
366 0: means infinite timeout - no checking done.
391 -1: report an infinite number of warnings.
397 Controls whether the panic kmsg data should be reported to Hyper-V.
431 users. Note, this is a temporary solution only. The correct long-term
464 By default they are equal to -1, which means generic allocation logic.
470 2) Toggle with non-default value will be set back to -1 by kernel after
472 fails, it is undefined if the value remains unmodified or is reset to -1.
481 0 - disable the hard lockup detector
483 1 - enable the hard lockup detector
485 The hard lockup detector monitors each CPU for its ability to respond to
486 timer interrupts. The mechanism utilizes CPU performance counter registers
487 that are programmed to generate Non-Maskable Interrupts (NMIs) periodically
488 while a CPU is busy. Hence, the alternative name 'NMI watchdog'.
495 to the guest kernel command line (see Documentation/admin-guide/kernel-parameters.rst).
506 is a performance penalty if remote memory is accessed by a CPU. When this
576 The only way to tune these values is to rebuild the kernel :-)
582 if your architecture did not always support 32-bit UIDs (i.e. arm,
584 applications that use the old 16-bit UID/GID system calls, if the
602 Controls the kernel's behavior when a CPU receives an NMI caused by
621 1: panic immediately. If the `panic` sysctl is also non-zero then the
694 Hints to the kernel how much CPU time it should be allowed to
697 will drop its sampling frequency to attempt to reduce its CPU
707 sampling rate no matter how CPU time it takes.
709 1-100:
711 percentage of CPU. Note: the kernel calculates an
716 how much CPU is consumed.
726 -1 Allow use of (almost) all events by all users
734 >=1 Disallow CPU event access by users without CAP_SYS_ADMIN
745 'perf record -g' or 'perf trace --call-graph fp'.
748 enabled, otherwise writing to this file will return -EBUSY.
756 Control size of per-cpu ring buffer not counted agains mlock limit.
766 instance, when using 'perf record -g' or 'perf trace --call-graph fp'.
769 enabled, otherwise writing to this file will return -EBUSY.
790 powersave-nap: (PPC only)
793 If set, Linux-PPC will use the 'nap' mode of powersaving,
809 - console_loglevel:
812 - default_message_loglevel:
815 - minimum_console_loglevel:
818 - default_console_loglevel:
827 Value from 0 - 10000 is allowed.
862 a one-time setting until next reboot: once set, it cannot be changed by
880 loaded to random addresses. Also for PIE-linked binaries, the
891 non-legacy applications that would be broken this way, so for most
900 reboot-cmd: (Sparc only)
908 rtsig-max & rtsig-nr:
911 The file rtsig-max can be used to tune the maximum number
915 rtsig-nr shows the number of RT signals currently queued.
923 platforms with asymmetric CPU topologies and having an Energy
937 sg-big-buff:
1000 -1 Legacy per-write sysctl value handling, with no printk warnings.
1019 to gather further debug information. If enabled, each cpu will
1035 0 - disable the soft lockup detector
1037 1 - enable the soft lockup detector
1043 the watchdog timer function, otherwise the NMI watchdog - if enabled - can
1055 The tradeoff is the performance impact: on a single CPU system kernel
1067 Non-zero if the kernel has been tainted. Numeric values, which can be
1083 4096 `(O)` externally-built ("out-of-tree") module was loaded
1091 See Documentation/admin-guide/tainted-kernels.rst for more information.
1094 threads-max:
1104 The minimum value that can be written to threads-max is 20.
1106 The maximum value that can be written to threads-max is given by the
1109 If a value outside of this range is written to threads-max an error
1114 available RAM pages threads-max is reduced accordingly.
1121 value is non-zero, unknown NMI is trapped and then panic occurs. At
1134 0 - disable both lockup detectors
1136 1 - enable both lockup detectors
1159 to re-enable cores that by default were not running the watchdog,
1166 echo 0,2-4 > /proc/sys/kernel/watchdog_cpumask