Home
last modified time | relevance | path

Searched refs:rules (Results 1 – 19 of 19) sorted by relevance

/tools/perf/util/
Dstrfilter.h30 struct strfilter *strfilter__new(const char *rules, const char **err);
43 const char *rules, const char **err);
56 const char *rules, const char **err);
Dstrfilter.c160 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/power/acpi/tools/ec/
DMakefile14 include ../../Makefile.rules
/tools/power/acpi/tools/acpidbg/
DMakefile22 include ../../Makefile.rules
/tools/testing/selftests/powerpc/nx-gzip/
DREADME10 /etc/udev/rules.d/99-nx-gzip.rules
/tools/testing/selftests/
Dlib.mk55 $(MAKE) --no-builtin-rules ARCH=$(ARCH) -C $(top_srcdir) headers_install
57 $(MAKE) --no-builtin-rules INSTALL_HDR_PATH=$$OUTPUT/usr \
DMakefile163 $(MAKE) --no-builtin-rules ARCH=$(ARCH) -C $(top_srcdir) headers_install
165 $(MAKE) --no-builtin-rules INSTALL_HDR_PATH=$$BUILD/usr \
/tools/power/acpi/tools/acpidump/
DMakefile46 include ../../Makefile.rules
/tools/lib/traceevent/Documentation/
Dlibtraceevent-filter.txt43 The _tep_filter_reset()_ function removes all rules from an event filter and
89 _pass:[TEP_ERRNO__NO_FILTER]_ - no rules in the filter.
93 The _tep_filter_copy()_ function returns 0 on success or -1 if not all rules
158 /* There are no rules in the filter */
/tools/build/Documentation/
DBuild.txt126 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/vm/
DMakefile21 MAKEFLAGS += --no-builtin-rules
/tools/perf/Documentation/
Ddb-export.txt20 backward and forward compatibility, by following some simple rules:
Dperf-probe.txt239 …ifying filter-out rule. You also can give several rules combined with "&" or "|", and fold those r…
Dsecurity.txt170 perf_event related rules:
Dtopdown.txt240 rules:
/tools/objtool/Documentation/
Dstack-validation.txt11 It enforces a set of rules on asm code and C inline assembly code so
119 To achieve the validation, objtool enforces the following rules:
135 Such code doesn't have to follow any of the other rules.
139 the architecture's back chain rules. This can by done in asm code
171 first make sure that the affected code follows the above rules.
/tools/memory-model/Documentation/
Drecipes.txt8 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
Dsimple.txt158 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
Dexplanation.txt264 The counterpart to ordering is a cycle. Ordering rules out cycles:
581 requirement takes the form of four coherency rules:
602 the rules of the Sequential Consistency memory model. (According to
864 system obey the four coherency rules.
877 grace periods obey the rules of RCU, in particular, the
882 the operational model's rules regarding cache coherence.
903 You can check that the four coherency rules imply that the rf, co, fr,
918 true: This LKMM axiom implies that the four coherency rules are
1665 a forbidden cycle. Thus the "rcu" axiom rules out this violation of
2416 rules used by the operational model to ensure cache coherence (that
[all …]