Home
last modified time | relevance | path

Searched refs:bindings (Results 1 – 12 of 12) sorted by relevance

/system/sepolicy/tools/
Dfuzzer_bindings_check.py30 bindings = json.loads(jsonFile.read())
31 return bindings
33 def check_fuzzer_exists(context_file, bindings): argument
50 if service_name not in bindings:
75 bindings = read_bindings(args.bindings)
78 check_fuzzer_exists(file, bindings)
DREADME84 … -b /path/to/binding.json Path to json file containing "service":[fuzzers...] bindings.
/system/extras/libatrace_rust/
DREADME.md1 # libatrace_rust - ATrace bindings for Rust
7 ### Using ATrace bindings directly
47 Compared to using the bindings directly, it has better instrumentation points and customizability.
112 ### ATrace bindings
121 The subscriber uses the bindings and adds its own overhead that depends on usage:
125 * Instant events (`event!`) add roughly 200 ns to the bindings - 1.5 vs 1.3 us.
/system/librustutils/
DAndroid.bp79 source_stem: "bindings",
110 source_stem: "bindings",
/system/security/prng_seeder/
DAndroid.bp26 source_stem: "bindings",
/system/security/keystore2/aaid/
DAndroid.bp38 source_stem: "bindings",
/system/core/libstats/pull_rust/
DAndroid.bp29 source_stem: "bindings",
/system/security/keystore2/apc_compat/
DAndroid.bp43 source_stem: "bindings",
/system/security/keystore2/src/crypto/
DAndroid.bp67 source_stem: "bindings",
/system/logging/liblog/
DAndroid.bp220 source_stem: "bindings",
/system/extras/libatrace_rust/benchmark/
DREADME.md3 Benchmarks to compare the performance of Rust ATrace bindings with directly calling the
/system/extras/simpleperf/
DAndroid.bp355 source_stem: "bindings",