Searched full:analysis (Results 1 – 25 of 80) sorted by relevance
1234
| /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
120 Static Analysis Tools
124 directly (**at compile time**) using **static analysis** tools. The tools
145 for the soundness of free operations, analysis of locking behavior, and further
149 Beware, though, that static analysis tools suffer from **false positives**.
159 Smatch does flow analysis and, if allowed to build the function database, it
160 also does cross function analysis. Smatch tries to answer questions like where
180 Coccinelle does no analysis of variable values, which is the strong point of
|
| /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
|
| D | common_timerlat_aa.rst | 7 disable auto-analysis, reducing rtla timerlat cpu usage
|
| D | rtla.rst | 5 Real-time Linux Analysis tool
|
| D | rtla-timerlat-top.rst | 38 Print the auto-analysis if the system hits the stop tracing condition. This option
117 The raw trace is saved in the **timerlat_trace.txt** file for further analysis.
|
| /Documentation/filesystems/xfs/ |
| D | xfs-self-describing-metadata.rst | 29 few days to perform such forensic analysis, so for at this scale root cause
30 analysis is entirely possible.
33 to analyse and so that analysis blows out towards weeks/months of forensic work.
34 Most of the analysis work is slow and tedious, so as the amount of analysis goes
37 required for basic forensic analysis of the filesystem structure.
49 Hence most of the time spent on forensic analysis is spent doing basic
59 of analysis. We can't protect against every possible type of error, but we can
77 metadata object at runtime, during forensic analysis or repair.
104 Another key information point in forensic analysis is knowing who the metadata
125 analysis is how recently the block was modified. Correlation of set of corrupted
|
| /Documentation/admin-guide/perf/ |
| D | dwc_pcie_pmu.rst | 17 - one 64-bit counter for Time Based Analysis (RX/TX data throughput and
24 Time Based Analysis
73 Time Based Analysis Event Usage
|
| /Documentation/admin-guide/ |
| D | index.rst | 62 application developers and system integrators doing analysis of the
64 analysis of kernel interactions with applications, and key kernel
|
| 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
|
| /Documentation/networking/device_drivers/atm/ |
| D | cxacru.rst | 78 - "channel analysis"
118 [4942255.666387] ATM dev 0: ADSL line: channel analysis
|
| /Documentation/trace/ |
| D | index.rst | 9 tracepoint-analysis
|
| /Documentation/admin-guide/kdump/ |
| D | index.rst | 6 This document includes overview, setup and installation, and analysis
|
| 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
156 analysis tools require a vmlinux with debug symbols in order to read
511 Analysis chapter
516 You can do limited analysis using GDB on the dump file copied out of
|
| /Documentation/devicetree/bindings/soc/mediatek/ |
| D | devapc.yaml | 14 analysis and countermeasures.
|
| /Documentation/devicetree/bindings/csky/ |
| D | pmu.txt | 6 it could count cpu's events for helping analysis performance issues.
|
| /Documentation/process/ |
| D | researcher-guidelines.rst | 88 analysis tools that produce actionable results.
111 testing, static or dynamic analysis programs, and any other tools or
134 This flaw was found using an experimental static analysis tool we are
|
| /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.
|
| /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
|
| /Documentation/networking/ |
| D | dctcp.rst | 41 "Analysis of DCTCP: Stability, Convergence, and Fairness"
|
| /Documentation/input/devices/ |
| D | cs461x.rst | 10 is present here, but have not tested completely. The button analysis
|
| /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
|
| /Documentation/hwmon/ |
| D | nsa320.rst | 56 read twice corrupting the output. The above analysis is based upon a sample
|
| /Documentation/misc-devices/ |
| D | dw-xdata-pcie.rst | 24 PCIe link performance analysis.
|
| /Documentation/admin-guide/thermal/ |
| D | intel_powerclamp.rst | 18 (*) Performance Analysis
49 Test/Analysis has been made in the areas of power, performance,
229 Performance Analysis
|
| /Documentation/translations/zh_CN/process/ |
| D | researcher-guidelines.rst | 100 This flaw was found using an experimental static analysis tool we are
|
1234