Lines Matching +full:enforce +full:- +full:video +full:- +full:mode
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
58 See Documentation/power/video.rst. This allows the video resume mode to be set,
124 Ctrl-Alt-Delete). Writing a value to this file which doesn't
125 correspond to a running process will result in ``-ESRCH``.
127 See also `ctrl-alt-del`_.
163 %d dump mode, matches ``PR_SET_DUMPABLE`` and
217 ctrl-alt-del
220 When the value in this file is 0, ctrl-alt-del is trapped and
228 mode, the ctrl-alt-del is intercepted by the program before it
273 See Documentation/driver-api/firmware/fallback-mechanisms.rst.
309 debug information. If enabled, arch-specific all-CPU stack dumping
329 See Documentation/admin-guide/lockup-watchdogs.rst for more information.
341 modern systems rely exclusively on the netlink-based uevent source and
355 1: Will non-maskably interrupt all CPUs and dump their backtraces when
412 -1: report an infinite number of warnings.
418 Controls whether the panic kmsg data should be reported to Hyper-V.
426 ignore-unaligned-usertrap
440 See also `unaligned-trap`_ and `unaligned-dump-stack`_. On ``ia64``,
478 The correct long-term solution is to do the permission checks at
551 By default they are equal to -1, which means generic allocation logic.
557 2) Toggle with non-default value will be set back to -1 by kernel after
559 fails, it is undefined if the value remains unmodified or is reset to -1.
583 that are programmed to generate Non-Maskable Interrupts (NMIs) periodically
592 Documentation/admin-guide/kernel-parameters.rst).
670 1: Will non-maskably interrupt all CPUs and dump their backtraces when
691 The only way to tune these values is to rebuild the kernel :-)
697 if your architecture did not always support 32-bit UIDs (i.e. arm,
699 applications that use the old 16-bit UID/GID system calls, if the
743 1 Panic immediately. If the `panic` sysctl is also non-zero then the
835 1-100 Attempt to throttle perf's sample rate to this
858 -1 Allow use of (almost) all events by all users.
879 '``perf record -g``' or '``perf trace --call-graph fp``'.
882 enabled, otherwise writing to this file will return ``-EBUSY``.
890 Control size of per-cpu ring buffer not counted against mlock limit.
900 instance, when using '``perf record -g``' or '``perf trace --call-graph fp``'.
903 enabled, otherwise writing to this file will return ``-EBUSY``.
924 powersave-nap (PPC only)
927 If set, Linux-PPC will use the 'nap' mode of powersaving,
928 otherwise the 'doze' mode will be used.
960 Value from 0 - 10000 is allowed.
976 While long term we enforce one message per `printk_ratelimit`_
996 a one-time setting until next reboot: once set, it cannot be changed by
1054 loaded to random addresses. Also for PIE-linked binaries, the
1065 non-legacy applications that would be broken this way, so for most
1074 real-root-dev
1077 See Documentation/admin-guide/initrd.rst.
1080 reboot-cmd (SPARC only)
1102 :doc:`accounting/delay-accounting.rst`). Enabling this feature incurs
1163 range of [0:600]. This could happen for instance if a powersave mode will
1171 See Documentation/userspace-api/seccomp_filter.rst.
1174 sg-big-buff
1244 -1 Legacy per-write sysctl value handling, with no printk warnings.
1325 stop-a (SPARC only)
1328 Controls Stop-A:
1331 0 Stop-A has no effect.
1332 1 Stop-A breaks to the PROM (default).
1335 Stop-A is always enabled on a panic, so that the user can return to
1342 See Documentation/admin-guide/sysrq.rst.
1348 Non-zero if the kernel has been tainted. Numeric values, which can be
1364 4096 `(O)` externally-built ("out-of-tree") module was loaded
1372 See Documentation/admin-guide/tainted-kernels.rst for more information.
1379 See Documentation/admin-guide/kernel-parameters.rst for more details on
1383 threads-max
1393 The minimum value that can be written to ``threads-max`` is 1.
1395 The maximum value that can be written to ``threads-max`` is given by the
1398 If a value outside of this range is written to ``threads-max`` an
1425 See Documentation/admin-guide/kernel-parameters.rst and
1426 Documentation/trace/boottime-trace.rst.
1429 .. _unaligned-dump-stack:
1431 unaligned-dump-stack (ia64)
1442 See also `ignore-unaligned-usertrap`_.
1445 unaligned-trap
1458 See also `ignore-unaligned-usertrap`_.
1465 value is non-zero, unknown NMI is trapped and then panic occurs. At
1477 will return ``-EPERM``. Once set to 1, this can't be cleared from the
1526 to re-enable cores that by default were not running the watchdog,
1533 echo 0,2-4 > /proc/sys/kernel/watchdog_cpumask