• Home
  • Raw
  • Download

Lines Matching +full:enforce +full:- +full:video +full:- +full:mode

5 .. See scripts/check-sysctl-docs to keep this up to date
14 ------------------------------------------------------------------------------
38 If BSD-style process accounting is enabled these values control
57 See :doc:`/power/video`. This allows the video resume mode to be set,
123 Ctrl-Alt-Delete). Writing a value to this file which doesn't
124 correspond to a running process will result in ``-ESRCH``.
126 See also `ctrl-alt-del`_.
162 %d dump mode, matches ``PR_SET_DUMPABLE`` and
216 ctrl-alt-del
219 When the value in this file is 0, ctrl-alt-del is trapped and
227 mode, the ctrl-alt-del is intercepted by the program before it
272 See :doc:`/driver-api/firmware/fallback-mechanisms`.
308 debug information. If enabled, arch-specific all-CPU stack dumping
328 See :doc:`/admin-guide/lockup-watchdogs` for more information.
349 1: Will non-maskably interrupt all CPUs and dump their backtraces when
406 -1: report an infinite number of warnings.
412 Controls whether the panic kmsg data should be reported to Hyper-V.
420 ignore-unaligned-usertrap
434 See also `unaligned-trap`_ and `unaligned-dump-stack`_. On ``ia64``,
472 The correct long-term solution is to do the permission checks at
544 By default they are equal to -1, which means generic allocation logic.
550 2) Toggle with non-default value will be set back to -1 by kernel after
552 fails, it is undefined if the value remains unmodified or is reset to -1.
576 that are programmed to generate Non-Maskable Interrupts (NMIs) periodically
584 to the guest kernel command line (see :doc:`/admin-guide/kernel-parameters`).
662 1: Will non-maskably interrupt all CPUs and dump their backtraces when
692 The only way to tune these values is to rebuild the kernel :-)
698 if your architecture did not always support 32-bit UIDs (i.e. arm,
700 applications that use the old 16-bit UID/GID system calls, if the
744 1 Panic immediately. If the `panic` sysctl is also non-zero then the
837 1-100 Attempt to throttle perf's sample rate to this
860 -1 Allow use of (almost) all events by all users.
881 '``perf record -g``' or '``perf trace --call-graph fp``'.
884 enabled, otherwise writing to this file will return ``-EBUSY``.
892 Control size of per-cpu ring buffer not counted agains mlock limit.
902 instance, when using '``perf record -g``' or '``perf trace --call-graph fp``'.
905 enabled, otherwise writing to this file will return ``-EBUSY``.
926 powersave-nap (PPC only)
929 If set, Linux-PPC will use the 'nap' mode of powersaving,
930 otherwise the 'doze' mode will be used.
962 Value from 0 - 10000 is allowed.
978 While long term we enforce one message per `printk_ratelimit`_
998 a one-time setting until next reboot: once set, it cannot be changed by
1050 loaded to random addresses. Also for PIE-linked binaries, the
1061 non-legacy applications that would be broken this way, so for most
1070 real-root-dev
1073 See :doc:`/admin-guide/initrd`.
1076 reboot-cmd (SPARC only)
1152 range of [0:600]. This could happen for instance if a powersave mode will
1160 See :doc:`/userspace-api/seccomp_filter`.
1163 sg-big-buff
1233 -1 Legacy per-write sysctl value handling, with no printk warnings.
1314 stop-a (SPARC only)
1317 Controls Stop-A:
1320 0 Stop-A has no effect.
1321 1 Stop-A breaks to the PROM (default).
1324 Stop-A is always enabled on a panic, so that the user can return to
1331 See :doc:`/admin-guide/sysrq`.
1337 Non-zero if the kernel has been tainted. Numeric values, which can be
1353 4096 `(O)` externally-built ("out-of-tree") module was loaded
1361 See :doc:`/admin-guide/tainted-kernels` for more information.
1368 See :doc:`/admin-guide/kernel-parameters` for more details on that particular
1371 threads-max
1381 The minimum value that can be written to ``threads-max`` is 1.
1383 The maximum value that can be written to ``threads-max`` is given by the
1386 If a value outside of this range is written to ``threads-max`` an
1413 See :doc:`/admin-guide/kernel-parameters` and
1414 :doc:`/trace/boottime-trace`.
1417 .. _unaligned-dump-stack:
1419 unaligned-dump-stack (ia64)
1430 See also `ignore-unaligned-usertrap`_.
1433 unaligned-trap
1446 See also `ignore-unaligned-usertrap`_.
1453 value is non-zero, unknown NMI is trapped and then panic occurs. At
1465 will return ``-EPERM``. Once set to 1, this can't be cleared from the
1524 to re-enable cores that by default were not running the watchdog,
1531 echo 0,2-4 > /proc/sys/kernel/watchdog_cpumask