Searched full:check (Results 1 – 25 of 700) sorted by relevance
12345678910>>...28
| /Documentation/RCU/ |
| D | lockdep.rst | 14 In addition, RCU provides the following primitives that check lockdep's
33 Check for RCU read-side critical section.
35 Check for RCU-bh read-side critical section.
37 Check for RCU-sched read-side critical section.
39 Check for SRCU read-side critical section.
41 Use explicit check expression "c" along with
45 Use explicit check expression "c" along with
49 Use explicit check expression "c" along with
53 Use explicit check expression "c" along with
57 Don't check. (Use sparingly, if at all.)
[all …]
|
| /Documentation/arch/x86/x86_64/ |
| D | machinecheck.rst | 4 Configurable sysfs parameters for the x86-64 machine check code
8 by the CPU. Uncorrected errors typically cause a machine check
9 (often with panic), corrected ones cause a machine check log entry.
17 When you see the "Machine check errors logged" message in the system
18 log then mcelog should run to collect and decode machine check entries
29 For more details about the x86 machine check architecture
|
| D | boot-options.rst | 10 Machine check
15 Disable machine check
17 Disable CMCI(Corrected Machine Check Interrupt) that
46 to make sure you log even machine check events that result
49 Disable boot machine check logging.
62 Force-enable recoverable machine check code paths
91 Don't check the IO-APIC timer. This can work around
145 systems because the BIOS will not go through the memory check.
190 disables parsing the HEST CMC error source to check if
|
| /Documentation/filesystems/ext4/ |
| D | mmp.rst | 13 open code will wait for twice the specified MMP check interval and check
19 While the filesystem is live, the kernel sets up a timer to re-check the
20 MMP block at the specified MMP check interval. To perform the re-check,
25 memory and on disk, and the re-check is complete.
65 - The MMP re-check interval, in seconds.
|
| /Documentation/ABI/testing/ |
| D | sysfs-mce | 9 machine check (often with panic), corrected ones cause a
10 machine check log entry.
12 For more details about the x86 machine check architecture
45 How often to poll for corrected machine check errors, in
52 0 means no polling for corrected machine check errors
63 Program to run when a machine check event is detected.
71 How long to wait for the other CPUs to machine check too on a
|
| D | sysfs-platform-dell-privacy-wmi | 30 For example to check which privacy devices are supported::
42 Allow user space to check current dell privacy device state.
67 For example to check all supported current privacy device states::
|
| D | sysfs-bus-most | 52 This is used to check and configure the MAC address.
60 This is used to check and configure the MAC address.
68 This is used to check and configure the MAC address.
76 This is used to check and configure the MEP filter address.
84 This is used to check and configure the MEP hash table.
92 This is used to check and configure the MEP hash table.
100 This is used to check and configure the MEP hash table.
108 This is used to check and configure the MEP hash table.
|
| D | configfs-acpi | 22 will be enumerated. To check if the operation is
23 successful the user must check the error code
|
| /Documentation/mm/ |
| D | page_table_check.rst | 4 Page Table Check
10 Page table check allows to harden the kernel by ensuring that some types of
13 Page table check performs extra verifications at the time when new pages become
18 performance and memory overhead associated with the page table check. Therefore,
20 extra hardening outweighs the performance costs. Also, because page table check
27 userfaultfd is the only user of such to sanity check wr-protect bit against
49 Enabling Page Table Check
67 MM states (except for limited "struct page" info). The page table check is a
76 page table check.
80 won't break the logic used in the page table check.
|
| /Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 4 OCFS2 file system - online file check
7 This document will describe OCFS2 online file check feature.
19 log. The user can try to check/fix this file via online filecheck feature.
23 This effort is to check/fix small issues which may hinder day-to-day operations
44 input to check/fix the file.
58 # echo "<inode>" > /sys/fs/ocfs2/<devname>/filecheck/check
59 # cat /sys/fs/ocfs2/<devname>/filecheck/check
83 3. The record cache is used to store the history of check/fix results. It's
|
| /Documentation/ |
| D | Makefile | 8 # Check for broken documentation file references
10 $(shell $(srctree)/scripts/documentation-file-ref-check --warn)
13 # Check for broken ABI files
39 # User-friendly check for sphinx-build
52 # User-friendly check for pdflatex and latexmk
121 @$(srctree)/scripts/sphinx-pre-install --version-check
135 @$(srctree)/scripts/sphinx-pre-install --version-check
147 @$(srctree)/scripts/sphinx-pre-install --version-check
160 @$(srctree)/scripts/sphinx-pre-install --version-check
162 …TEXOPTS)" $(DENY_VF) -C $(BUILDDIR)/$(var)/latex || sh $(srctree)/scripts/check-variable-fonts.sh …
[all …]
|
| D | Kconfig | 9 This option makes the Kernel to check for missing dependencies,
22 scripts/get_abi.pl. Add a check to verify them.
|
| /Documentation/ABI/removed/ |
| D | sysfs-mce | 14 Tolerance level. When a machine check exception occurs for a
15 non corrected machine check the kernel can take different
18 Since machine check exceptions can happen any time it is
36 from a machine check exception. Current x86 CPUs generally
|
| D | sysfs-selinux-checkreqprot | 11 to check the protection requested by userspace for mmap/mprotect
17 at boot was changed starting in Linux v4.4 to 0 (i.e. check the
23 check the actual protections being applied upon mmap/mprotect calls.
|
| /Documentation/staging/ |
| D | xz.rst | 54 check, make sure that you don't use some other integrity check type
58 use ``--check=crc32`` or ``--check=none`` to override the default
59 ``--check=crc64``.
65 by the decoder; you can only change the integrity check type (or
91 xz --threads=1 --check=crc32 --lzma2=dict=512KiB inputfile
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-firmware-zynqmp | 99 is compiled with CHECK_HEALTHY_BOOT, it will check the healthy
147 Check over temperature config ID is selected or not
154 Check over temperature config ID is selected or not
161 Check external watchdog config ID is selected or not
168 Check external watchdog config ID is selected or not
212 Check whether the over temperature feature is enabled or not
220 Check whether the over temperature feature is disabled or not
228 Check whether the over temperature limit is configured or not
236 Check whether the external watchdog feature is enabled or not
244 Check whether the external watchdog feature is disabled or not
[all …]
|
| /Documentation/i2c/ |
| D | functionality.rst | 11 the client needs some way to check whether an adapter has the needed
18 For the most up-to-date list of functionality constants, please check
93 to let the client drivers check for the support of SMBus functions
102 Before a client tries to attach to an adapter, or even do tests to check
104 check whether the needed functionality is present. The typical way to do
118 this adapter and there's no point in going on. If the check above is
126 Note that the check above doesn't tell whether the functionalities are
137 to use the /dev interface. You will still have to check whether the
|
| /Documentation/arch/arm64/ |
| D | memory-tagging-extension.rst | 58 Tag Check Faults
66 tag check fault.
75 thread, asynchronously following one or multiple tag check faults,
87 - ``PR_MTE_TCF_NONE`` - *Ignore* tag check faults
89 - ``PR_MTE_TCF_SYNC`` - *Synchronous* tag check fault mode
90 - ``PR_MTE_TCF_ASYNC`` - *Asynchronous* tag check fault mode
92 If no modes are specified, tag check faults are ignored. If a single
97 The current tag check fault configuration can be read using the
114 ``PR_MTE_TCF_SYNC``, the kernel makes a best effort to check its user
150 checking mode, the user program may set multiple tag check fault mode
[all …]
|
| /Documentation/dev-tools/ |
| D | checkuapi.rst | 7 The UAPI checker (``scripts/check-uapi.sh``) is a shell script which
14 This section will describe the options with which ``check-uapi.sh``
19 check-uapi.sh [-b BASE_REF] [-p PAST_REF] [-j N] [-l ERROR_LOG] [-i] [-q] [-v]
75 % ./scripts/check-uapi.sh
99 % ./scripts/check-uapi.sh
123 % ./scripts/check-uapi.sh -i
149 % ./scripts/check-uapi.sh -i
174 % ./scripts/check-uapi.sh
187 % ./scripts/check-uapi.sh -p HEAD~2
226 % ./scripts/check-uapi.sh
[all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 27 If your card isn't listed there, you might check the source code for
29 card, you can check if one of the existing entries does work for you
37 you might want to check the video4linux mailing list archive first...
40 speakers connected directly to the grabber board. Hint: check the
87 card installed, you might to check out if you can read these registers
104 value for all array elements, useful to check
|
| /Documentation/translations/zh_CN/staging/ |
| D | xz.rst | 57 或LZMA_CHECK_CRC32。使用xz命令行工具时，使用--check=none或--check=crc32。
68 xz --check=crc32 --lzma2=dict=512KiB inputfile
|
| /Documentation/process/ |
| D | submit-checklist.rst | 21 2) Check your patch for general style as detailed in
62 Check your code with tools
65 1) Check for trivial violations with the patch style checker prior to
70 2) Check cleanly with sparse.
90 Use ``make htmldocs`` or ``make pdfdocs`` to check the build and
|
| /Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 14 /* Check if any requests are pending for VCPU @vcpu. */
17 /* Check if VCPU @vcpu has request @req pending. */
24 * Check if VCPU @vcpu has request @req pending. When the request is
194 kvm_request_pending() check and before it has entered guest mode, as kick
202 the last kvm_request_pending() check;
208 !kvm_request_pending() on its last check and then not receiving an IPI for
210 the check. This is done by way of the Dekker memory barrier pattern
236 As only one IPI is needed to get a VCPU to check for any/all requests,
260 receiving VCPU, as the final kvm_request_pending() check does for
286 to check if it should awaken. One reason to do so is to provide
|
| /Documentation/admin-guide/ |
| D | mono.rst | 21 Once the Mono CLR support has been installed, just check that
61 4) Check that ``.exe`` binaries can be ran without the need of a
69 If this fails with a permission denied error, check
|
| D | bug-bisect.rst | 51 3. Check if the functionality that regressed works in the kernel you just built.
66 After issuing one of these two commands, Git will usually check out another
90 codebase and check if that fixes your bug; if that is the case, it validates
94 To try this, update your clone and check out latest mainline. Then tell Git
103 check out its latest codebase and try a revert there.
105 If a revert succeeds, build and test another kernel to check if reverting
|
12345678910>>...28