Home
last modified time | relevance | path

Searched full:correctness (Results 1 – 25 of 174) sorted by relevance

1234567

/linux/tools/testing/selftests/arm64/mte/
H A Dcheck_buffer_fill.c425 "Check buffer correctness by byte with sync err mode and mmap memory\n"); in main()
427 "Check buffer correctness by byte with async err mode and mmap memory\n"); in main()
429 "Check buffer correctness by byte with sync err mode and mmap/mprotect memory\n"); in main()
431 "Check buffer correctness by byte with async err mode and mmap/mprotect memory\n"); in main()
459 "Check buffer write correctness by block with sync mode and mmap memory\n"); in main()
461 "Check buffer write correctness by block with async mode and mmap memory\n"); in main()
463 "Check buffer write correctness by block with tag fault ignore and mmap memory\n"); in main()
/linux/Documentation/features/locking/lockdep/
H A Darch-support.txt4 # description: arch supports the runtime locking correctness debug facility
/linux/Documentation/ABI/testing/
H A Ddebugfs-iio-ad946739 additional information about the data correctness is given.
/linux/fs/befs/
H A Dinode.c14 * Validates the correctness of the befs inode
/linux/lib/crypto/tests/
H A DKconfig60 If you're only interested in correctness testing, leave this disabled.
/linux/Documentation/virt/kvm/devices/
H A Dvfio.rst13 of those groups/devices important to the correctness and acceleration
/linux/fs/gfs2/
H A Dtrace_gfs2.h93 * Correctness: Ordering of local lock state vs. I/O requests
94 * Correctness: Responses to remote demote requests
322 * Correctness: pin/unpin vs. disk I/O ordering
440 * Correctness: Test of disard generation vs. blocks allocated
/linux/Documentation/locking/
H A Dlockdep-design.rst1 Runtime locking correctness validator
281 Proof of 100% correctness:
285 correctness) in the sense that for every simple, standalone single-task
294 task/context) for the validator to be able to prove correctness. (For
303 once, to prove locking correctness - instead of having to trigger every
/linux/tools/perf/tests/
H A Dutil.c30 * The correctness of this value was verified by running this test with in test_sha1()
/linux/arch/x86/platform/efi/
H A Defi_thunk_64.S75 // This return instruction is not needed for correctness, as it will
/linux/include/crypto/
H A Db128ops.h41 in respect of its properties, including, but not limited to, correctness
/linux/arch/arm/kernel/
H A Dentry-v7m.S79 @ correctness they don't need to be restored. So only r8-r11 must be
/linux/drivers/comedi/drivers/
H A Dni_tio.h168 * have already validated the correctness of this value.
/linux/lib/
H A DKconfig.debug1374 bool "Lock debugging: prove locking correctness"
1415 the proof of observed correctness is also maintained for an
2721 Tests the API contract and implementation correctness of sysctl.
2779 Tests the linear_ranges logic correctness.
3207 tristate "Test module for correctness and stress of objpool"
3212 correctness verification and concurrent testings of objects
3238 tristate "KUnit Test for correctness and stress of ratelimit" if !KUNIT_ALL_TESTS
3243 for correctness verification and concurrent testings of rate
3271 various scenarios, including edge cases, to ensure correctness.
3298 This test suite verifies the correctness of gcd() across various
H A Dfind_bit_benchmark.c10 * is good enough test for correctness.
/linux/Documentation/admin-guide/sysctl/
H A Dindex.rst29 The consequences are that I won't guarantee the correctness of
/linux/samples/kfifo/
H A Dinttype-example.c88 /* check the correctness of all values in the fifo */ in testfunc()
H A Drecord-example.c100 /* check the correctness of all values in the fifo */ in testfunc()
H A Dbytestream-example.c95 /* check the correctness of all values in the fifo */ in testfunc()
/linux/drivers/net/ethernet/intel/i40e/
H A Di40e_ddp.c215 * Checks correctness of pkg header: Version, size too big/small, and
279 * Checks correctness and loads DDP profile to the NIC. The function is
/linux/fs/pstore/
H A Dftrace.c23 /* This doesn't need to be atomic: speed is chosen over correctness here. */
/linux/Documentation/filesystems/bcachefs/
H A DSubmittingPatches.rst71 language that can do ergonomic embedded correctness proofs. Hitting an assert
/linux/Documentation/networking/
H A Dfib_trie.rst147 To alleviate any doubts about the correctness of the route selection process,
/linux/drivers/spi/
H A Dspi-pxa2xx-platform.c106 /* Validate the SSP type correctness */ in pxa2xx_spi_init_pdata()
/linux/kernel/locking/
H A Dlockdep_internals.h5 * Runtime locking correctness validator

1234567