Searched full:analysis (Results 1 – 25 of 49) sorted by relevance
12
| /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
|
| /Documentation/trace/ |
| D | index.rst | 9 tracepoint-analysis
|
| D | tracepoint-analysis.rst | 188 6. Higher-Level Analysis with Helper Scripts
220 7. Lower-Level Analysis with PCL
224 were generating events within the kernel. To begin this sort of analysis, the
|
| /Documentation/networking/device_drivers/atm/ |
| D | cxacru.rst | 78 - "channel analysis"
118 [4942255.666387] ATM dev 0: ADSL line: channel 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 and installation, and analysis
53 use analysis tools such as the GNU Debugger (GDB) and the Crash tool to
149 analysis tools require a vmlinux with debug symbols in order to read
492 Analysis chapter
497 You can do limited analysis using GDB on the dump file copied out of
|
| /Documentation/admin-guide/ |
| D | perf-security.rst | 15 units (PMU) [2]_ and Perf collect and expose for performance analysis.
95 performance analysis of monitored processes or a system. For example,
185 analysis. Per-user per-cpu perf_event_mlock_kb locking limit is
193 monitored and captured for later analysis. Per-user per-cpu
200 monitored and captured for later analysis. Per-user per-cpu
|
| /Documentation/devicetree/bindings/csky/ |
| D | pmu.txt | 6 it could count cpu's events for helping analysis performance issues.
|
| /Documentation/networking/ |
| D | dctcp.rst | 41 "Analysis of DCTCP: Stability, Convergence, and Fairness"
|
| D | net_dim.rst | 22 change moderation parameters for a channel, usually by performing an analysis on
|
| /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/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
|
| D | static-keys.rst | 211 5) Static keys / jump label analysis, results (x86_64):
|
| /Documentation/hwmon/ |
| D | nsa320.rst | 56 read twice corrupting the output. The above analysis is based upon a sample
|
| /Documentation/networking/devlink/ |
| D | devlink-region.rst | 14 or dump commands. This allows future analysis on the created snapshots.
|
| /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
|
| /Documentation/kbuild/ |
| D | gcc-plugins.rst | 10 compiler [1]_. They are useful for runtime instrumentation and static analysis.
|
| /Documentation/vm/ |
| D | page_owner.rst | 21 buffer for later analysis and it would change system behaviour with more
|
| D | slub.rst | 334 mode also simplifies the analysis of slabs' behaviour, because its
336 pushes the analysis from looking through the numbers (tons of numbers)
337 to something easier -- visual analysis.
|
| /Documentation/dev-tools/ |
| D | kcsan.rst | 97 Selective analysis
296 6. **Analysis Accuracy:** For observed executions, due to using a sampling
297 strategy, the analysis is *unsound* (false negatives possible), but aims to
|
| /Documentation/scheduler/ |
| D | sched-deadline.rst | 14 3.2 Schedulability Analysis for Uniprocessor Systems
15 3.3 Schedulability Analysis for Multiprocessor Systems
368 3.2 Schedulability Analysis for Uniprocessor Systems
409 In any case, this kind of analysis is too complex as well as too
413 3.3 Schedulability Analysis for Multiprocessor Systems
512 Analysis. Proceedings of the 24th IEEE Real-Time Systems Symposium, 2003.
513 9 - T. Baker. An Analysis of EDF Schedulability on a Multiprocessor.
|
| /Documentation/x86/ |
| D | orc-unwinder.rst | 134 creating a GCC plugin to assist objtool with its analysis. But for now,
|
| /Documentation/trace/coresight/ |
| D | coresight-cpu-debug.rst | 25 analysis for panic.
|
| /Documentation/x86/x86_64/ |
| D | boot-options.rst | 66 analysis less effective if the bios sets thresholds for memory
|
12