| /linux/Documentation/ABI/testing/ |
| H A D | evm | 24 0 Enable HMAC validation and creation
25 1 Enable digital signature validation
27 runtime. Not supported if HMAC validation and
36 will enable HMAC validation and creation
42 will enable HMAC and digital signature validation and
49 will enable digital signature validation, permit
|
| /linux/Documentation/gpu/amdgpu/display/ |
| H A D | index.rst | 17 DC Code validation
21 synchronization effort between repositories and exhaustive validation. In the
35 * Prepare a branch with those patches for our validation team. If there is an
44 seriously, and we never merge anything that fails our validation. Follows an
59 * Compilation validation with the latest GCC and Clang from LTS distro.
|
| /linux/tools/objtool/Documentation/ |
| H A D | objtool.txt | 18 - Stack unwinding metadata validation -- useful for helping to ensure
24 - Retpoline validation -- ensures that all indirect calls go through
31 - Return thunk validation -- validates return thunks are used for
37 - Return thunk untraining validation -- validate that all entry paths
40 - Non-instrumentation validation -- validates non-instrumentable
48 - Uaccess validation -- validates uaccess rules for a proper
51 - Straight Line Speculation validation -- validates certain SLS
54 - Indirect Branch Tracking validation -- validates Intel CET IBT rules
83 - If noinstr validation is enabled, it also runs on vmlinux.o, with all
107 Stack validation
[all...] |
| /linux/Documentation/hwmon/ |
| H A D | sht15.rst | 57 * If a CRC validation fails, a soft reset command is sent, which resets
65 set it to true to enable CRC validation of the readings (default to false).
|
| /linux/fs/afs/ |
| H A D | Makefile | 33 validation.o \
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-ext-ctrls.rst | 385 control, or the validation step failed (see below), then
389 Before controls are read from/written to hardware a validation
402 came from the validation step (meaning that the hardware was not
407 ``error_idx`` to ``count`` if the validation failed. This has the
409 control failed the validation. If the validation was successful
416 also no need to handle the validation step in this special way, so
418 validation step instead of to ``count``. This means that if
421 actual control that failed the validation step. Unfortunately,
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-buildid-list.txt | 32 Don't do ownership validation.
|
| H A D | perf-kmem.txt | 33 Don't do ownership validation
|
| /linux/drivers/gpu/drm/amd/pm/powerplay/inc/ |
| H A D | power_state.h | 157 struct PP_StateValidationBlock validation; member
|
| /linux/Documentation/arch/x86/ |
| H A D | orc-unwinder.rst | 18 stack metadata validation (CONFIG_STACK_VALIDATION). After analyzing
94 stack metadata validation feature, objtool already follows all code
97 validation to ORC data generation.
142 stack metadata validation feature, which is described in detail in
|
| /linux/Documentation/userspace-api/netlink/ |
| H A D | specs.rst | 19 - policy tables for input attribute validation
158 which attributes are allowed in a nest or refining the validation criteria.
172 Allows narrowing down fields and changing validation criteria
251 Input validation constraints used by the kernel. User space should query
255 The validation policy in the kernel is formed by combining the type
|
| /linux/drivers/thunderbolt/ |
| H A D | Kconfig | 42 and robustness validation during manufacturing. Should not be
|
| /linux/Documentation/gpu/ |
| H A D | vc4.rst | 87 V3D binner command list (BCL) validation
|
| /linux/Documentation/userspace-api/fwctl/ |
| H A D | fwctl.rst | 215 provided by user space are mapped to the appropriate scope. If the validation is
216 done in the driver then the validation can read a 'command effects' report from
217 the device, or hardwire the enforcement. If the validation is done in the FW,
247 that the existing kernel pattern of allowing drivers to delegate validation to
|
| /linux/Documentation/core-api/irq/ |
| H A D | irqflags-tracing.rst | 43 excluded from the irq-tracing [and lock validation] mechanism via
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm_event_log.rst | 28 contents. The PCR contents are used to provide the validation of the
|
| /linux/Documentation/leds/ |
| H A D | leds-class.rst | 102 meets the requirements pointed out here. It performs validation of the LED class
104 the validation fails for it. So far the script supports validation
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | overview.rst | 69 * If user-configured, validation and associations are built at
|
| /linux/sound/usb/ |
| H A D | clock.c | 607 * external clock source. Try again without validation in set_sample_rate_v2v3()
608 * and we will do another validation after setting the in set_sample_rate_v2v3()
623 goto validation; in set_sample_rate_v2v3()
654 validation: in set_sample_rate_v2v3()
|
| /linux/Documentation/networking/ |
| H A D | driver.rst | 10 Address validation
|
| H A D | vxlan.rst | 72 perform protocol-aware offloads, like checksum validation offload of
|
| /linux/Documentation/driver-api/media/ |
| H A D | mc-core.rst | 240 Link validation
243 Link validation is performed by :c:func:`media_pipeline_start()`
251 Subsystems should facilitate link validation by providing subsystem specific
|
| /linux/Documentation/core-api/ |
| H A D | netlink.rst | 70 Defines whether the kernel validation policy is ``global`` i.e. the same for all
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-self-describing-metadata.rst | 82 integrity check, and this is done by adding CRC32c validation to the metadata
113 owner field in the metadata object, we can immediately do top down validation to
163 body, but in general most of the per-field validation is handled by the
179 object specific metadata validation. If any of these checks fail, then the
|
| /linux/Documentation/filesystems/ |
| H A D | mount_api.rst | 54 parameter description for validation at registration time and querying by a
386 the parameter parsing and validation hooks.
728 struct as this will provide validation on registration (if
760 This performs some validation checks on a parameter description. It
762 log errors to the kernel log buffer if validation fails.
|