| /tools/perf/util/ |
| D | strfilter.h | 30 struct strfilter *strfilter__new(const char *rules, const char **err);
43 const char *rules, const char **err);
56 const char *rules, const char **err);
|
| D | strfilter.c | 160 struct strfilter *strfilter__new(const char *rules, const char **err) in strfilter__new() argument
166 filter->root = strfilter_node__new(rules, &ep); in strfilter__new()
179 const char *rules, const char **err) in strfilter__append() argument
184 if (!filter || !rules) in strfilter__append()
187 right = strfilter_node__new(rules, &ep); in strfilter__append()
207 int strfilter__or(struct strfilter *filter, const char *rules, const char **err) in strfilter__or() argument
209 return strfilter__append(filter, true, rules, err); in strfilter__or()
212 int strfilter__and(struct strfilter *filter, const char *rules, in strfilter__and() argument
215 return strfilter__append(filter, false, rules, err); in strfilter__and()
|
| /tools/testing/selftests/bpf/progs/ |
| D | twfw.c | 36 struct rules_map rules SEC(".maps");
47 struct rule* rule = bpf_map_lookup_elem(&rules, &key); in twfw_verifier()
|
| /tools/testing/selftests/landlock/ |
| D | fs_test.c | 742 const struct rule rules[]) in create_ruleset() argument
749 ASSERT_NE(NULL, rules) in create_ruleset()
753 ASSERT_NE(NULL, rules[0].path) in create_ruleset()
765 for (i = 0; rules[i].path; i++) { in create_ruleset()
766 if (!rules[i].access) in create_ruleset()
769 add_path_beneath(_metadata, ruleset_fd, rules[i].access, in create_ruleset()
770 rules[i].path); in create_ruleset()
777 const struct rule rules[] = { in TEST_F_FORK() local
787 _metadata, rules[0].access | LANDLOCK_ACCESS_FS_READ_DIR, in TEST_F_FORK()
788 rules); in TEST_F_FORK()
[all …]
|
| /tools/perf/tests/shell/lib/ |
| D | perf_metric_validation.py | 41 self.rules = None
403 for rule in self.rules:
456 def remove_unsupported_rules(self, rules): argument
458 for rule in rules:
477 rules = data['RelationshipRules']
479 self.rules = self.remove_unsupported_rules(rules)
487 self.rules.append(pctgrule)
491 for r in self.rules:
497 data = {'RelationshipRules': self.rules, 'SupportedMetrics': [
548 for r in self.rules:
|
| /tools/power/acpi/tools/ec/ |
| D | Makefile | 14 include ../../Makefile.rules
|
| /tools/power/acpi/tools/acpidbg/ |
| D | Makefile | 22 include ../../Makefile.rules
|
| /tools/power/acpi/tools/pfrut/ |
| D | Makefile | 16 include ../../Makefile.rules
|
| /tools/testing/selftests/powerpc/nx-gzip/ |
| D | README | 10 /etc/udev/rules.d/99-nx-gzip.rules
|
| /tools/power/acpi/tools/acpidump/ |
| D | Makefile | 47 include ../../Makefile.rules
|
| /tools/build/Documentation/ |
| D | Build.txt | 126 The build framework provides standard compilation rules to handle .S and .c
154 - Dependency rules generated by 'gcc -Wp,-MD,...'
161 Single rules
|
| /tools/testing/selftests/net/netfilter/ |
| D | nft_audit.sh | 28 reset rules t c
|
| /tools/objtool/Documentation/ |
| D | objtool.txt | 32 ("noinstr") code rules, preventing instrumentation in low-level C
39 - Uaccess validation -- validates uaccess rules for a proper
45 - Indirect Branch Tracking validation -- validates Intel CET IBT rules
99 the validity of its stack metadata. It enforces a set of rules on asm
196 To achieve the validation, objtool enforces the following rules:
212 Such code doesn't have to follow any of the other rules.
216 the architecture's back chain rules. This can by done in asm code
253 first make sure that the affected code follows the above rules.
|
| /tools/perf/Documentation/ |
| D | db-export.txt | 20 backward and forward compatibility, by following some simple rules:
|
| D | perf-probe.txt | 239 …ifying filter-out rule. You also can give several rules combined with "&" or "|", and fold those r…
|
| D | security.txt | 170 perf_event related rules:
|
| D | topdown.txt | 299 rules:
|
| /tools/testing/selftests/mm/ |
| D | Makefile | 34 MAKEFLAGS += --no-builtin-rules
|
| /tools/memory-model/Documentation/ |
| D | recipes.txt | 8 and the third section provides a few rules of thumb.
34 just as if the compiler had followed all the relevant rules.
465 This situation is accounted for in the rules of thumb below.
568 However, if you find yourself having to stretch these rules of thumb
|
| D | simple.txt | 158 keep-things-simple rules for RCU are "do not write in read-side code"
162 These rules are illustrated by the functions foo_update_a() and
|
| D | access-marking.txt | 211 code's synchronization rules.
224 rules as are other type qualifiers such as const and volatile.
|
| D | explanation.txt | 265 The counterpart to ordering is a cycle. Ordering rules out cycles:
634 requirement takes the form of four coherency rules:
655 the rules of the Sequential Consistency memory model. (According to
917 system obey the four coherency rules.
930 grace periods obey the rules of RCU, in particular, the
935 the operational model's rules regarding cache coherence.
956 You can check that the four coherency rules imply that the rf, co, fr,
971 true: This LKMM axiom implies that the four coherency rules are
1748 a forbidden cycle. Thus the "rcu" axiom rules out this violation of
2660 rules used by the operational model to ensure cache coherence (that
[all …]
|
| /tools/bpf/bpftool/Documentation/ |
| D | bpftool-gen.rst | 38 The rules of BPF static linking are mostly the same as for user-space
|