Home
last modified time | relevance | path

Searched refs:relevant (Results 1 – 9 of 9) sorted by relevance

/tools/power/cpupower/debug/i386/
A Ddump_psb.c22 static long relevant; variable
112 if (relevant != 0) { in decode_psb()
113 if (relevant!= pst->cpuid) in decode_psb()
164 relevant = strtol(optarg, NULL, 16); in main()
/tools/power/pm-graph/
A DREADME215 file is a tabular list of the tests with relevant info and links. The
227 These are the relevant arguments to use for testing:
257 These are the relevant commands to use after testing is complete:
262 current folder. summary.html is a table of tests with relevant info sorted
/tools/perf/Documentation/
A Dperf-list.txt98 section of the [AMD Processor Programming Reference (PPR)] relevant to the
117 [AMD Processor Programming Reference (PPR)] relevant to the family, model
A Dperf-intel-pt.txt284 'p' is also not relevant to Intel PT. So only options 'u' and 'k' are
/tools/memory-model/
A DREADME169 Categorizes the relevant instructions, including memory
/tools/bpf/bpftool/Documentation/
A Dbpftool-prog.rst202 print to the standard output (as plain text, or JSON if relevant option was
/tools/memory-model/Documentation/
A Drecipes.txt34 just as if the compiler had followed all the relevant rules.
A Daccess-marking.txt135 the other accesses to the relevant shared variables. But please note
A Dlitmus-tests.txt244 people know which of the several thousand relevant litmus tests were

Completed in 14 milliseconds