Searched refs:validation (Results 1 – 25 of 87) sorted by relevance
1234
| /linux-6.1.9/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
|
| D | sysfs-class-firmware-attributes | 199 password-validation) and must be cleared once the session is over.
210 require password validation.
|
| /linux-6.1.9/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.1.9/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.1.9/Documentation/devicetree/bindings/ |
| D | writing-schema.rst | 86 validation of DT files.
99 validation. There are currently 2 transformations the tools perform.
149 In order to perform validation of DT source files, use the ``dtbs_check`` target::
154 necessary to use ``dt_binding_check`` to get all the validation errors in the
|
| D | submitting-patches.rst | 23 vocabulary and YAML file format. The DT binding files must pass validation
|
| /linux-6.1.9/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-ext-ctrls.rst | 335 control, or the validation step failed (see below), then
339 Before controls are read from/written to hardware a validation
352 came from the validation step (meaning that the hardware was not
357 ``error_idx`` to ``count`` if the validation failed. This has the
359 control failed the validation. If the validation was successful
366 also no need to handle the validation step in this special way, so
368 validation step instead of to ``count``. This means that if
371 actual control that failed the validation step. Unfortunately,
|
| /linux-6.1.9/tools/perf/Documentation/ |
| D | perf-buildid-list.txt | 32 Don't do ownership validation.
|
| D | perf-kmem.txt | 33 Don't do ownership validation
|
| D | perf-mem.txt | 37 Don't do ownership validation
|
| D | perf-annotate.txt | 36 Don't do ownership validation.
|
| /linux-6.1.9/drivers/gpu/drm/amd/pm/powerplay/inc/ |
| D | power_state.h | 156 struct PP_StateValidationBlock validation; member
|
| /linux-6.1.9/Documentation/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.1.9/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.1.9/Documentation/gpu/ |
| D | vc4.rst | 68 V3D binner command list (BCL) validation
|
| /linux-6.1.9/drivers/thunderbolt/ |
| D | Kconfig | 37 validation during manufacturing. Should not be enabled by distro
|
| /linux-6.1.9/sound/usb/ |
| D | clock.c | 555 goto validation; in set_sample_rate_v2v3()
586 validation: in set_sample_rate_v2v3()
|
| /linux-6.1.9/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 43 excluded from the irq-tracing [and lock validation] mechanism via
|
| /linux-6.1.9/Documentation/security/tpm/ |
| D | tpm_event_log.rst | 28 contents. The PCR contents are used to provide the validation of the
|
| /linux-6.1.9/Documentation/networking/ |
| D | vxlan.rst | 72 perform protocol-aware offloads, like checksum validation offload of
|
| /linux-6.1.9/Documentation/driver-api/media/ |
| D | mc-core.rst | 266 Link validation
269 Link validation is performed by :c:func:`media_pipeline_start()`
277 Subsystems should facilitate link validation by providing subsystem specific
|
| /linux-6.1.9/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 81 integrity check, and this is done by adding CRC32c validation to the metadata
112 owner field in the metadata object, we can immediately do top down validation to
162 body, but in general most of the per-field validation is handled by the
178 object specific metadata validation. If any of these checks fail, then the
|
| D | mount_api.rst | 54 parameter description for validation at registration time and querying by a
387 the parameter parsing and validation hooks.
737 struct as this will provide validation on registration (if
783 This performs some validation checks on a parameter description. It
785 log errors to the kernel log buffer if validation fails.
|
| /linux-6.1.9/tools/testing/selftests/tc-testing/creating-plugins/ |
| D | AddingPlugins.txt | 100 The check_args method is so that the plugin can do validation on
|
| /linux-6.1.9/Documentation/driver-api/firmware/ |
| D | fw_upload.rst | 10 device itself to perform any validation on the data received. Firmware
|
1234