Lines Matching refs:to
12 The files in this directory can be used to tune and monitor
14 kernel. Since some of the files _can_ be used to screw up your
15 system, it is advisable to read both documentation and source
114 See Doc*/kernel/power/video.txt, it allows mode of video boot to be
123 Up to Linux 3.17, it enabled/disabled automatic recomputing of msgmni
137 version. The reason for this encoding is that this used to match the
164 The s390 hardware allows an operating system to send a notification
165 to a service organization (callhome) in case of an operating system panic.
168 nothing happens in case of a kernel panic. If this value is set to "1"
169 the complete kernel oops message is send to the IBM customer service
184 core_pattern is used to specify a core dumpfile pattern name.
191 and core_uses_pid is set, then .PID will be appended to
211 the rest of the pattern as a command to run. The core dump will be
212 written to the standard input of that program instead of to a file.
218 This sysctl is only applicable when core_pattern is configured to pipe
219 core files to a user space helper (when the first character of
221 to an application, it is occasionally useful for the collecting
222 application to gather data about the crashing process from its
223 /proc/pid directory. In order to do this safely, the kernel must wait
224 for the collecting process to exit, so as not to remove the crashing
229 processes may be piped to user space applications in parallel. If
234 process is not guaranteed access to /proc/<crashing pid>/). This
235 value defaults to 0.
242 core_uses_pid to 1, the coredump filename becomes core.PID.
244 and core_uses_pid is set, then .PID will be appended to
252 sent to the init(1) program to handle a graceful restart.
253 When, however, the value is > 0, Linux's reaction to a Vulcan
259 ever reaches the kernel tty layer, and it's up to the program
260 to decide what to do with it.
267 from using dmesg(8) to view messages from the kernel's log buffer.
268 When dmesg_restrict is set to (0) there are no restrictions. When
269 dmesg_restrict is set set to (1), users must have CAP_SYSLOG to use
279 These files can be used to set the NIS/YP domainname and the
290 domainname "frop.org", not to be confused with the NIS (Network
329 Possible values to set are in range {0..LONG_MAX/HZ}.
335 The maximum number of warnings to report. During a check interval
347 value defaults to 0 (false: kexec_load enabled), but can be set to 1
349 the toggle cannot be set back to false. This allows a kexec image to be
350 loaded before disabling the syscall, allowing a system to set up (and
361 When kptr_restrict is set to (0), the default, there are no restrictions.
363 When kptr_restrict is set to (1), kernel pointers printed using the %pK
365 and effective user and group ids are equal to the real ids. This is
368 a setuid binary) then %pK will not leak kernel pointers to unprivileged
370 solution is to do the permission checks at open() time. Consider removing
372 to protect against uses of %pK in dmesg(8) if leaking kernel pointer
373 values to unprivileged users is a concern.
375 When kptr_restrict is set to (2), kernel pointers printed using
382 Controls the number of words to print when dumping the raw
396 A toggle value indicating if modules are allowed to be loaded
397 in an otherwise modular kernel. This toggle defaults to off
400 to false. Generally used with the "kexec_load_disabled" toggle.
406 These three toggles allows to specify desired id for next allocated IPC
409 By default they are equal to -1, which means generic allocation logic.
410 Possible values to set are in range {0..INT_MAX}.
414 it's up to userspace, how to handle an object with "wrong" id.
415 2) Toggle with non-default value will be set back to -1 by kernel after
422 This parameter can be used to control the NMI watchdog
428 The hard lockup detector monitors each CPU for its ability to respond to
430 that are programmed to generate Non-Maskable Interrupts (NMIs) periodically
438 to the guest kernel command line (see Documentation/kernel-parameters.txt).
445 balancing. Memory is moved automatically to nodes
453 be migrated to a local memory node.
457 guarantee. If the target workload is already bound to NUMA nodes then this
469 Automatic NUMA balancing scans tasks address space and unmaps pages to
470 detect if pages are properly placed or if the data should be migrated to a
471 memory node local to where the task is running. Every "scan delay" the task
484 rate, the more quickly a tasks memory is migrated to a local node if the
485 workload pattern changes and minimises performance impact due to remote
489 numa_balancing_scan_period_min_ms is the minimum time in milliseconds to
496 numa_balancing_scan_period_max_ms is the maximum time in milliseconds to
518 The only way to tune these values is to rebuild the kernel :-)
525 i386, m68k, sh, and sparc32), a fixed UID and GID will be returned to
529 These sysctls allow you to change the value of the fixed UID and GID.
546 0: try to continue operation
559 0: try to continue operation.
568 to continue operation. For many environments such as scientific
580 Calls panic() in the WARN() path when set to 1. This is useful to avoid
581 a kernel rebuild when attempting to kdump at the location of a WARN().
591 Hints to the kernel how much CPU time it should be allowed to
592 use to handle perf sampling events. If the perf subsystem
594 will drop its sampling frequency to attempt to reduce its CPU
598 unexpectedly take too long to execute, the NMIs can become
599 stacked up next to each other so much that nothing else is
600 allowed to execute.
605 1-100: attempt to throttle perf's sample rate to this
608 100% of that expected length. Even if this is set to
610 length is exceeded. Set to 0 if you truly do not care
619 reaches this value, it wraps back to a minimum PID value.
628 kernel tries to allocate a number starting from this one.
650 this will be printed to the console
653 - minimum_console_loglevel: minimum (highest) value to which
680 seconds, we do allow a burst of messages to pass through.
688 This option can be used to select the type of process address
698 loaded to random addresses. Also for PIE-linked binaries, the
710 systems it is safe to choose full randomization.
720 ??? This seems to be a way to give an argument to the Sparc
721 ROM/Flash boot loader. Maybe to tell it what to do after
728 The file rtsig-max can be used to tune the maximum number
743 There shouldn't be any reason to change this value. If
764 This value can be used to query and set the run time limit
766 Shared memory segments up to 1Gb are now supported in the
767 kernel. This value defaults to SHMMAX.
775 segments are allowed to exist without association with any process, and
779 also destroy segments that were created, but never attached to, on exit
780 from the process. The only use left for IPC_RMID is to immediately
787 Note that if you change this from 0 to 1, already created segments
798 Each write syscall must fully contain the sysctl value to be
802 perform writes to a sysctl file descriptor when the file position
805 will append to the sysctl value buffer. Anything past the max length
806 of the sysctl value buffer will be ignored. Writes to numeric sysctl
815 when a soft lockup condition is detected as to whether or not
816 to gather further debug information. If enabled, each cpu will
817 be issued an NMI and instructed to capture stack trace.
830 This parameter can be used to control the soft lockup detector.
837 from running. The mechanism depends on the CPUs ability to respond to timer
838 interrupts which are needed for the 'watchdog/N' threads to be woken up by
884 The minimum value that can be written to threads-max is 20.
885 The maximum value that can be written to threads-max is given by the
887 If a value outside of this range is written to threads-max an error
909 This parameter can be used to disable or enable the soft lockup detector
928 This value can be used to control the frequency of hrtimer and NMI
933 tunable to zero will disable lockup detection altogether.