Lines Matching +full:use +full:- +full:minimum +full:- +full:ecc
5 .. See scripts/check-sysctl-docs to keep this up to date
13 Documentation/admin-guide/sysctl/index.rst.
15 ------------------------------------------------------------------------------
39 If BSD-style process accounting is enabled these values control
71 The machine hardware name, the same output as ``uname -m``
129 Ctrl-Alt-Delete). Writing a value to this file which doesn't
130 correspond to a running process will result in ``-ESRCH``.
132 See also `ctrl-alt-del`_.
236 ctrl-alt-del
239 When the value in this file is 0, ctrl-alt-del is trapped and
247 mode, the ctrl-alt-del is intercepted by the program before it
260 ``CAP_SYSLOG`` to use ``dmesg(8)``.
303 See Documentation/driver-api/firmware/fallback-mechanisms.rst.
308 * ``force_sysfs_fallback``, when set to 1, forces the use of the
357 debug information. If enabled, arch-specific all-CPU stack dumping
377 See Documentation/admin-guide/lockup-watchdogs.rst for more information.
389 modern systems rely exclusively on the netlink-based uevent source and
403 1: Will non-maskably interrupt all CPUs and dump their backtraces when
446 0 (default) means use ``hung_task_timeout_secs`` as checking
460 -1: report an infinite number of warnings.
466 Controls whether the panic kmsg data should be reported to Hyper-V.
474 ignore-unaligned-usertrap
488 See also `unaligned-trap`_.
500 -EPERM) for unprivileged processes not in the io_uring_group group.
504 always fails with -EPERM. Existing io_uring instances can still be
514 to create an io_uring instance. If io_uring_group is set to -1 (the
529 allowing a system to set up (and later use) an image without it being
542 -1 Unlimited calls to kexec. This is the default setting.
571 The correct long-term solution is to do the permission checks at
573 Consider removing world read permissions from files that use %pK, and
647 By default they are equal to -1, which means generic allocation logic.
653 2) Toggle with non-default value will be set back to -1 by kernel after
655 fails, it is undefined if the value remains unmodified or is reset to -1.
679 that are programmed to generate Non-Maskable Interrupts (NMIs) periodically
688 Documentation/admin-guide/kernel-parameters.rst).
739 promotion throughput. The per-node max promotion throughput in MB/s
757 1: Will non-maskably interrupt all CPUs and dump their backtraces when
787 The only way to tune these values is to rebuild the kernel :-)
793 if your architecture did not always support 32-bit UIDs (i.e. arm,
795 applications that use the old 16-bit UID/GID system calls, if the
813 When you use the software watchdog, the recommended setting is 60.
828 and you can use this option to take a crash dump.
839 1 Panic immediately. If the `panic` sysctl is also non-zero then the
863 dealt with than an uncorrected parity/ECC error get propagated.
927 use to handle perf sampling events. If the perf subsystem
941 1-100 Attempt to throttle perf's sample rate to this
954 Controls use of the performance events system by unprivileged
961 with respect to CAP_PERFMON use cases.
964 -1 Allow use of (almost) all events by all users.
985 '``perf record -g``' or '``perf trace --call-graph fp``'.
987 This can only be done when no events are in use that have callchains
988 enabled, otherwise writing to this file will return ``-EBUSY``.
996 Control size of per-cpu ring buffer not counted against mlock limit.
1006 instance, when using '``perf record -g``' or '``perf trace --call-graph fp``'.
1008 This can only be done when no events are in use that have callchains
1009 enabled, otherwise writing to this file will return ``-EBUSY``.
1048 reaches this value, it wraps back to a minimum PID value.
1060 powersave-nap (PPC only)
1063 If set, Linux-PPC will use the 'nap' mode of powersaving,
1085 minimum_console_loglevel minimum (highest) value to which
1096 Value from 0 - 10000 is allowed.
1103 the minimum length of time between these messages (in seconds).
1132 a one-time setting until next reboot: once set, it cannot be changed by
1159 * ``urandom_min_reseed_secs``: obsolete (used to determine the minimum
1184 loaded to random addresses. Also for PIE-linked binaries, the
1195 non-legacy applications that would be broken this way, so for most
1204 real-root-dev
1207 See Documentation/admin-guide/initrd.rst.
1210 reboot-cmd (SPARC only)
1225 requirements for EAS but you do not want to use it, change
1226 this value to 0. On Non-EAS platforms, write operation fails and
1233 Documentation/accounting/delay-accounting.rst. Enabling this feature incurs
1247 Max allowed *minimum* utilization.
1302 See Documentation/userspace-api/seccomp_filter.rst.
1305 sg-big-buff
1362 from the process. The only use left for ``IPC_RMID`` is to immediately
1380 -1 Legacy per-write sysctl value handling, with no printk warnings.
1446 On x86, each "split lock" imposes a system-wide performance penalty. On larger
1448 denials of service to well-behaved and potentially more important users.
1459 0 Disable the mitigation mode - just warns the split lock on kernel log
1461 1 Enable the mitigation mode (this is the default) - penalizes the split
1484 stop-a (SPARC only)
1487 Controls Stop-A:
1490 0 Stop-A has no effect.
1491 1 Stop-A breaks to the PROM (default).
1494 Stop-A is always enabled on a panic, so that the user can return to
1501 See Documentation/admin-guide/sysrq.rst.
1507 Non-zero if the kernel has been tainted. Numeric values, which can be
1523 4096 `(O)` externally-built ("out-of-tree") module was loaded
1531 See Documentation/admin-guide/tainted-kernels.rst for more information.
1538 See Documentation/admin-guide/kernel-parameters.rst for more details on
1542 threads-max
1552 The minimum value that can be written to ``threads-max`` is 1.
1554 The maximum value that can be written to ``threads-max`` is given by the
1557 If a value outside of this range is written to ``threads-max`` an
1584 See Documentation/admin-guide/kernel-parameters.rst and
1585 Documentation/trace/boottime-trace.rst.
1588 unaligned-trap
1601 See also `ignore-unaligned-usertrap`_.
1608 value is non-zero, unknown NMI is trapped and then panic occurs. At
1620 will return ``-EPERM``. Once set to 1, this can't be cleared from the
1679 to re-enable cores that by default were not running the watchdog,
1686 echo 0,2-4 > /proc/sys/kernel/watchdog_cpumask