| /linux/tools/perf/Documentation/ |
| H A D | perf-kwork.txt | 107 Only analyze samples within given time window: <start>,<stop>. Times
137 Only analyze samples within given time window: <start>,<stop>. Times
176 Only analyze samples within given time window: <start>,<stop>. Times
206 Only analyze samples within given time window: <start>,<stop>. Times
|
| H A D | perf-kvm.txt | 94 analyze events which occur on this vcpu. (default: all vcpus)
131 analyze events which occur on this vcpu. (default: all vcpus)
|
| H A D | perf-kmem.txt | 72 Only analyze samples within given time window: <start>,<stop>. Times
|
| H A D | tips.txt | 54 To analyze cache line scalability issues use perf c2c record ... ; perf c2c report
67 To analyze particular parallelism levels, try: perf report --latency --parallelism=32-64
|
| H A D | perf-lock.txt | 15 You can analyze various lock behaviours
|
| /linux/tools/tracing/rtla/src/ |
| H A D | common.c | 226 if (ops->analyze) in run_tool()
227 ops->analyze(tool, stopped); in run_tool()
|
| H A D | common.h | 142 void (*analyze)(struct osnoise_tool *tool, bool stopped); member
|
| H A D | timerlat_top.c | 933 .analyze = timerlat_analyze,
|
| H A D | timerlat_hist.c | 1158 .analyze = timerlat_analyze,
|
| /linux/Documentation/tools/rtla/ |
| H A D | rtla.rst | 17 analyze the real-time properties of Linux. But instead of testing Linux
|
| H A D | rtla-timerlat-top.rst | 124 kernel developers to analyze scheduling delays.
|
| /linux/tools/tracing/rtla/ |
| H A D | README.txt | 3 The rtla meta-tool includes a set of commands that aims to analyze
|
| /linux/Documentation/trace/ |
| H A D | index.rst | 6 developers and system administrators to analyze and debug system
|
| /linux/arch/loongarch/ |
| H A D | Kconfig.debug | 24 traces. It unwind the stack frame based on prologue code analyze. Symbol
|
| /linux/Documentation/dev-tools/ |
| H A D | gpio-sloppy-logic-analyzer.rst | 18 appeared on these lines. One way to use it is to analyze external traffic
|
| H A D | testing-overview.rst | 123 In addition to testing a running kernel, one can also analyze kernel source code
|
| /linux/Documentation/trace/rv/ |
| H A D | monitor_rtapp.rst | 90 problem. Application developers must analyze the warnings to make a proper
|
| /linux/Documentation/userspace-api/ |
| H A D | mseal.rst | 157 but it is *crucial to thoroughly analyze the mapping's lifetime* prior to
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-zoned.rst | 145 will analyze the device zone configuration, determine where to place the
|
| /linux/Documentation/admin-guide/media/ |
| H A D | faq.rst | 147 DVB sniffer program to monitor, analyze, debug, dump
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-dpipe.rst | 36 In many situations trying to analyze systems failure solely based on the
|
| /linux/Documentation/mm/ |
| H A D | page_owner.rst | 12 When we need to know about status of all pages, we can get and analyze
|
| /linux/Documentation/driver-api/nvdimm/ |
| H A D | btt.rst | 212 On startup, we analyze the BTT flog to create our list of free blocks. We walk
|
| /linux/Documentation/admin-guide/kdump/ |
| H A D | vmcoreinfo.rst | 12 analyze a kernel's memory layout.
|
| /linux/Documentation/process/ |
| H A D | deprecated.rst | 283 the compiler to correctly analyze array sizes (via sizeof(),
|