Searched full:analysis (Results 1 – 25 of 257) sorted by relevance
1234567891011
| /Linux-v6.1/tools/perf/Documentation/ |
| D | perf-kwork.txt | 24 'perf kwork timehist' provides an analysis of kernel work events.
105 string is ',x.y') then analysis starts at the beginning of the file. If
106 stop time is not given (i.e, time string is 'x.y,') then analysis goes
135 string is ',x.y') then analysis starts at the beginning of the file. If
136 stop time is not given (i.e, time string is 'x.y,') then analysis goes
174 string is ',x.y') then analysis starts at the beginning of the file. If
175 stop time is not given (i.e, time string is 'x.y,') then analysis goes
|
| D | perf-sched.txt | 39 'perf sched timehist' provides an analysis of scheduling events.
162 string is ',x.y') then analysis starts at the beginning of the file. If
163 stop time is not given (i.e, time string is 'x.y,') then analysis goes
|
| D | perf-kmem.txt | 74 string is ',x.y') then analysis starts at the beginning of the file. If
75 stop time is not given (i.e, time string is 'x.y,') then analysis goes
|
| D | perf.txt | 6 perf - Performance analysis tools for Linux
70 that provide a framework for all things performance analysis. It
|
| D | examples.txt | 174 analysis done over ten 1-second intervals:
217 expressive power of system analysis and performance
218 analysis.
|
| D | perf-c2c.txt | 19 The perf c2c tool provides means for Shared Data C2C/HITM analysis. It allows
131 The perf c2c record command setup options related to HITM cacheline analysis
163 The perf c2c report command displays shared data analysis. It comes in two
|
| D | perf-archive.txt | 16 buildids found so that analysis of perf.data contents can be possible on another
|
| /Linux-v6.1/Documentation/dev-tools/ |
| D | testing-overview.rst | 85 Dynamic Analysis Tools
88 The kernel also supports a number of dynamic analysis tools, which attempt to
118 Static Analysis Tools
122 directly (**at compile time**) using **static analysis** tools. The tools
143 for the soundness of free operations, analysis of locking behavior, and further
147 Beware, though, that static analysis tools suffer from **false positives**.
157 Smatch does flow analysis and, if allowed to build the function database, it
158 also does cross function analysis. Smatch tries to answer questions like where
178 Coccinelle does no analysis of variable values, which is the strong point of
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 28 few days to perform such forensic analysis, so for at this scale root cause
29 analysis is entirely possible.
32 to analyse and so that analysis blows out towards weeks/months of forensic work.
33 Most of the analysis work is slow and tedious, so as the amount of analysis goes
36 required for basic forensic analysis of the filesystem structure.
48 Hence most of the time spent on forensic analysis is spent doing basic
58 of analysis. We can't protect against every possible type of error, but we can
76 metadata object at runtime, during forensic analysis or repair.
103 Another key information point in forensic analysis is knowing who the metadata
124 analysis is how recently the block was modified. Correlation of set of corrupted
|
| /Linux-v6.1/Documentation/tools/rtla/ |
| D | index.rst | 4 The realtime Linux analysis tool
7 RTLA provides a set of tools for the analysis of the kernel's realtime
|
| /Linux-v6.1/Documentation/process/ |
| D | researcher-guidelines.rst | 61 analysis tools that produce actionable results.
84 testing, static or dynamic analysis programs, and any other tools or
107 This flaw was found using an experimental static analysis tool we are
|
| /Linux-v6.1/Documentation/networking/device_drivers/atm/ |
| D | cxacru.rst | 78 - "channel analysis"
118 [4942255.666387] ATM dev 0: ADSL line: channel analysis
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | perf-security.rst | 15 units (PMU) [2]_ and Perf collect and expose for performance analysis.
98 performance analysis of monitored processes or a system. For example,
242 analysis. Per-user per-cpu perf_event_mlock_kb locking limit is
250 monitored and captured for later analysis. Per-user per-cpu
257 monitored and captured for later analysis. Per-user per-cpu
|
| /Linux-v6.1/Documentation/driver-api/mtd/ |
| D | nand_ecc.rst | 169 Analysis 0
279 Analysis 1
295 byte. A quick analysis:
410 Analysis 2
462 Analysis 3
499 Analysis 4
535 Analysis 5
590 Analysis 6
660 Analysis 7
677 Analysis 8
|
| /Linux-v6.1/Documentation/trace/rv/ |
| D | runtime-verification.rst | 74 De Oliveira, Daniel Bristot. *Automata-based formal analysis and
93 event analysis. If the system generates events at a frequency higher than the
108 buffer, not even considering collecting the trace for user-space analysis.
|
| /Linux-v6.1/tools/testing/selftests/vm/ |
| D | test_vmalloc.sh | 75 echo "for deep performance analysis as well as stress testing."
108 echo "# Performance analysis"
|
| /Linux-v6.1/drivers/net/fddi/skfp/h/ |
| D | targetos.h | 63 #define FDDI_TRACE(string, arg1, arg2, arg3) // Performance analysis.
65 #define NDD_TRACE(string, arg1, arg2, arg3) // Performance analysis.
|
| /Linux-v6.1/Documentation/staging/ |
| D | lzo.rst | 11 of this analysis is lib/lzo/lzo1x_decompress_safe.c. No analysis was made on
197 analysis of the decompression code available in Linux 3.16-rc5, and updated
|
| /Linux-v6.1/drivers/iio/ |
| D | TODO | 11 iio_claim_direct.(Requires analysis of the purpose of the lock.)
|
| /Linux-v6.1/Documentation/trace/ |
| D | index.rst | 9 tracepoint-analysis
|
| /Linux-v6.1/include/kunit/ |
| D | test-bug.h | 3 * KUnit API allowing dynamic analysis tools to interact with KUnit tests
|
| /Linux-v6.1/tools/perf/arch/sh/util/ |
| D | dwarf-regs.c | 12 * Generic dwarf analysis helpers
|
| /Linux-v6.1/Documentation/driver-api/thermal/ |
| D | intel_powerclamp.rst | 18 (*) Performance Analysis
47 Test/Analysis has been made in the areas of power, performance,
225 Performance Analysis
|
| /Linux-v6.1/Documentation/admin-guide/kdump/ |
| D | kdump.rst | 5 This document includes overview, setup, installation, and analysis
56 you can use analysis tools such as the GNU Debugger (GDB) and the Crash
160 analysis tools require a vmlinux with debug symbols in order to read
545 Analysis chapter
550 You can do limited analysis using GDB on the dump file copied out of
|
| D | index.rst | 6 This document includes overview, setup and installation, and analysis
|
1234567891011
