/freebsd/share/man/man9/ |
H A D | buf.9 | 40 It also supports a relatively primitive byte-granular valid range and dirty 68 VM buffers also keep track of a byte-granular dirty range and valid range. 76 operation creates a 'hole' the byte-granular valid range is left alone and 78 Thus the whole byte-granular
|
H A D | kmsan.9 | 73 runtime component and use hidden, byte-granular shadow state to determine 204 Unlike the shadow map, the origin map is not byte-granular, but consists of 4-byte
|
/freebsd/contrib/pjdfstest/tests/granular/ |
H A D | 01.t | 3 # $FreeBSD: head/tools/regression/pjdfstest/tests/granular/01.t 211352 2010-08-15 21:24:17Z pjd $ 5 desc="NFSv4 granular permissions checking - ACL_READ_ATTRIBUTES and ACL_WRITE_ATTRIBUTES"
|
H A D | 04.t | 3 # $FreeBSD: head/tools/regression/pjdfstest/tests/granular/04.t 211352 2010-08-15 21:24:17Z pjd $ 5 desc="NFSv4 granular permissions checking - ACL_WRITE_OWNER"
|
H A D | 00.t | 3 # $FreeBSD: head/tools/regression/pjdfstest/tests/granular/00.t 211352 2010-08-15 21:24:17Z pjd $ 5 desc="NFSv4 granular permissions checking - WRITE_DATA vs APPEND_DATA on directories"
|
H A D | 02.t | 3 # $FreeBSD: head/tools/regression/pjdfstest/tests/granular/02.t 211352 2010-08-15 21:24:17Z pjd $ 5 desc="NFSv4 granular permissions checking - ACL_READ_ACL and ACL_WRITE_ACL"
|
H A D | 03.t | 3 # $FreeBSD: head/tools/regression/pjdfstest/tests/granular/03.t 211352 2010-08-15 21:24:17Z pjd $ 5 desc="NFSv4 granular permissions checking - DELETE and DELETE_CHILD"
|
H A D | 05.t | 3 # $FreeBSD: head/tools/regression/pjdfstest/tests/granular/05.t 211352 2010-08-15 21:24:17Z pjd $ 5 desc="NFSv4 granular permissions checking - DELETE and DELETE_CHILD with directories"
|
/freebsd/crypto/openssh/ |
H A D | ssherr.h | 21 /* XXX are these too granular? not granular enough? I can't decide - djm */
|
/freebsd/contrib/ntp/sntp/m4/ |
H A D | hms_search_lib.m4 | 1 dnl Helper function to manage granular libraries
|
/freebsd/tests/sys/pjdfstest/tests/ |
H A D | Makefile | 25 TESTS_SUBDIRS+= granular
|
/freebsd/tests/sys/fs/fusefs/ |
H A D | Makefile | 9 # out, so we get more granular reporting.
|
/freebsd/sys/amd64/include/ |
H A D | sgxreg.h | 92 * The ATTRIBUTES data structure is comprised of bit-granular fields that
|
/freebsd/contrib/llvm-project/llvm/include/llvm/IR/ |
H A D | AutoUpgrade.h | 35 /// This is a more granular function that simply checks an intrinsic function
|
/freebsd/contrib/llvm-project/clang/include/clang/Basic/ |
H A D | Sarif.h | 189 "ThreadFlows require a character granular source range!"); in setRange() 354 "SARIF Results require character granular source ranges!"); in setLocations()
|
/freebsd/sys/dev/mlx4/mlx4_core/ |
H A D | mlx4_fw_qos.c | 66 /* Granular Qos (per VF) section */
|
/freebsd/contrib/llvm-project/clang/lib/StaticAnalyzer/Core/ |
H A D | SarifDiagnostics.cpp | 111 /// and converts to a Character granular CharSourceRange.
|
/freebsd/sys/contrib/device-tree/Bindings/arm/ |
H A D | arm,vexpress-juno.yaml | 37 further subvariants are released of the core tile, even more fine-granular
|
/freebsd/contrib/llvm-project/clang/include/clang/StaticAnalyzer/Frontend/ |
H A D | CheckerRegistry.h | 66 // FIXME: The Clang version string is not particularly granular;
|
/freebsd/share/doc/papers/kerntune/ |
H A D | 3.t | 57 routines will make its output more granular.
|
/freebsd/etc/mtree/ |
H A D | BSD.tests.dist | 921 granular
|
/freebsd/share/doc/psd/18.gprof/ |
H A D | present.me | 194 routines will make its output more granular.
|
/freebsd/share/doc/psd/05.sysman/ |
H A D | 2.2.t | 397 provides locking with file granularity. More granular
|
/freebsd/crypto/openssl/doc/man7/ |
H A D | provider-keymgmt.pod | 175 regardless of their more granular classification.
|
/freebsd/secure/lib/libcrypto/man/man7/ |
H A D | provider-keymgmt.7 | 302 regardless of their more granular classification.
|