Searched refs:validation (Results 1 – 25 of 106) sorted by relevance
12345
/linux-6.12.1/Documentation/ABI/testing/ |
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-6.12.1/Documentation/gpu/amdgpu/display/ |
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-6.12.1/tools/objtool/Documentation/ |
D | objtool.txt | 18 - Stack unwinding metadata validation -- useful for helping to ensure 24 - Retpoline validation -- ensures that all indirect calls go through 31 - Non-instrumentation validation -- validates non-instrumentable 39 - Uaccess validation -- validates uaccess rules for a proper 42 - Straight Line Speculation validation -- validates certain SLS 45 - Indirect Branch Tracking validation -- validates Intel CET IBT rules 71 - If noinstr validation is enabled, it also runs on vmlinux.o, with all 95 Stack validation 98 Objtool's stack validation feature analyzes every .o file and ensures 196 To achieve the validation, objtool enforces the following rules: [all …]
|
/linux-6.12.1/Documentation/hwmon/ |
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-6.12.1/fs/afs/ |
D | Makefile | 31 validation.o \
|
/linux-6.12.1/Documentation/userspace-api/media/v4l/ |
D | vidioc-g-ext-ctrls.rst | 369 control, or the validation step failed (see below), then 373 Before controls are read from/written to hardware a validation 386 came from the validation step (meaning that the hardware was not 391 ``error_idx`` to ``count`` if the validation failed. This has the 393 control failed the validation. If the validation was successful 400 also no need to handle the validation step in this special way, so 402 validation step instead of to ``count``. This means that if 405 actual control that failed the validation step. Unfortunately,
|
/linux-6.12.1/Documentation/devicetree/bindings/ |
D | writing-schema.rst | 108 validation of DT files. 121 validation. There are currently 2 transformations the tools perform. 171 In order to perform validation of DT source files, use the ``dtbs_check`` target:: 176 necessary to use ``dt_binding_check`` to get all the validation errors in the
|
D | submitting-patches.rst | 28 vocabulary and YAML file format. The DT binding files must pass validation
|
/linux-6.12.1/tools/perf/Documentation/ |
D | perf-buildid-list.txt | 32 Don't do ownership validation.
|
D | perf-kmem.txt | 33 Don't do ownership validation
|
/linux-6.12.1/drivers/gpu/drm/amd/pm/powerplay/inc/ |
D | power_state.h | 157 struct PP_StateValidationBlock validation; member
|
/linux-6.12.1/Documentation/arch/x86/ |
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-6.12.1/Documentation/userspace-api/netlink/ |
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-6.12.1/drivers/thunderbolt/ |
D | Kconfig | 42 and robustness validation during manufacturing. Should not be
|
/linux-6.12.1/Documentation/gpu/ |
D | vc4.rst | 87 V3D binner command list (BCL) validation
|
/linux-6.12.1/sound/usb/ |
D | clock.c | 601 goto validation; in set_sample_rate_v2v3() 632 validation: in set_sample_rate_v2v3()
|
/linux-6.12.1/Documentation/core-api/irq/ |
D | irqflags-tracing.rst | 43 excluded from the irq-tracing [and lock validation] mechanism via
|
/linux-6.12.1/Documentation/security/tpm/ |
D | tpm_event_log.rst | 28 contents. The PCR contents are used to provide the validation of the
|
/linux-6.12.1/Documentation/leds/ |
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-6.12.1/Documentation/driver-api/media/ |
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-6.12.1/Documentation/networking/ |
D | vxlan.rst | 72 perform protocol-aware offloads, like checksum validation offload of
|
D | driver.rst | 10 Address validation
|
/linux-6.12.1/Documentation/filesystems/xfs/ |
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-6.12.1/Documentation/core-api/ |
D | netlink.rst | 70 Defines whether the kernel validation policy is ``global`` i.e. the same for all
|
/linux-6.12.1/Documentation/gpu/imagination/ |
D | uapi.rst | 167 :doc: IOCTL validation helpers
|
12345