Searched refs:validator (Results 1 – 10 of 10) sorted by relevance
| /linux/drivers/md/persistent-data/ |
| A D | dm-block-manager.c | 348 const struct dm_block_validator *validator; member
360 aux->validator = NULL; in dm_block_manager_alloc_callback()
368 if (aux->validator) { in dm_block_manager_write_callback()
369 aux->validator->prepare_for_write(aux->validator, (struct dm_block *) buf, in dm_block_manager_write_callback()
446 if (unlikely(!aux->validator)) { in dm_bm_validate_buffer()
457 aux->validator = v; in dm_bm_validate_buffer()
459 if (unlikely(aux->validator != v)) { in dm_bm_validate_buffer()
461 aux->validator->name, v ? v->name : "NULL", in dm_bm_validate_buffer()
596 aux->validator = v; in dm_bm_write_lock_zero()
|
| /linux/Documentation/gpu/ |
| A D | vc4.rst | 91 :doc: Command list validator for VC4.
99 Shader validator for VC4
102 :doc: Shader validator for VC4.
|
| /linux/Documentation/locking/ |
| A D | lockdep-design.rst | 1 Runtime locking correctness validator
11 The basic object the validator operates upon is a 'class' of locks.
19 The validator tracks the 'usage state' of lock-classes, and it tracks
25 dependency just means the order ever happened. The validator maintains a
27 the validator will shoot a splat if incorrect.
134 The validator detects and reports lock usage that violates these
151 validator will find such dependency circle in arbitrary complexity,
206 lock, the lock ordering is fully correct. The validator does not
210 In order to teach the validator about this correct usage model, new
287 kernel, the validator proves it with a 100% certainty that no
[all …]
|
| /linux/kernel/trace/ |
| A D | trace_events_user.c | 1088 struct user_event_validator *validator, *next; in user_event_destroy_validators() local
1092 list_del(&validator->user_event_link); in user_event_destroy_validators()
1093 kfree(validator); in user_event_destroy_validators()
1112 struct user_event_validator *validator; in user_event_add_field() local
1135 validator = kmalloc(sizeof(*validator), GFP_KERNEL_ACCOUNT); in user_event_add_field()
1137 if (!validator) { in user_event_add_field()
1142 validator->flags = validator_flags; in user_event_add_field()
1143 validator->offset = offset; in user_event_add_field()
1557 struct user_event_validator *validator; in user_event_validate() local
1562 pos = data + validator->offset; in user_event_validate()
[all …]
|
| /linux/Documentation/core-api/irq/ |
| A D | irqflags-tracing.rst | 33 trace_hardirqs_off()/trace_hardirqs_on() functions. The lock validator
48 turn itself off. I.e. the lock validator will still be reliable. There
|
| /linux/sound/usb/ |
| A D | clock.c | 43 bool (*validator)(void *, int, int), in find_uac_clock_desc()
50 if (validator(cs, id, proto)) in find_uac_clock_desc()
78 #define DEFINE_FIND_HELPER(name, obj, validator, type2, type3) \ argument
84 return find_uac_clock_desc(ctrl_intf, id, validator, \
|
| /linux/tools/perf/tests/shell/lib/ |
| A D | perf_metric_validation.py | 587 validator = Validator(args.rule, reportf, debug=args.debug,
590 ret = validator.test()
|
| /linux/Documentation/filesystems/ |
| A D | affs.rst | 238 no way to fix a garbled filesystem without an Amiga (disk validator)
|
| /linux/Documentation/dev-tools/ |
| A D | testing-overview.rst | 105 * lockdep is a locking correctness validator. See
|
| /linux/Documentation/admin-guide/ |
| A D | kernel-parameters.txt | 6869 kernel versions where the validator will fail and reset the ring buffer
|
Completed in 45 milliseconds