Home
last modified time | relevance | path

Searched +full:ftrace +full:- +full:size (Results 1 – 18 of 18) sorted by relevance

/Documentation/trace/
Dboottime-trace.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Boot-time tracing
12 Boot-time tracing allows users to trace boot-time process including
13 device initialization with full features of ftrace including per-event
14 filter and actions, histograms, kprobe-events and synthetic-events,
23 boot config file [1]_. All options are under "ftrace." or "kernel."
27 .. [1] See :ref:`Documentation/admin-guide/bootconfig.rst <bootconfig>`
28 .. [2] See :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>`
30 Ftrace Global Options
31 ---------------------
[all …]
Dftrace-design.rst12 ------------
20 ftrace.txt file.
23 their kernel should make it all the way to dynamic ftrace support.
27 -------------
29 Ftrace relies on these features being implemented:
30 - STACKTRACE_SUPPORT - implement save_stack_trace()
31 - TRACE_IRQFLAGS_SUPPORT - implement include/asm/irqflags.h
35 --------------------
43 $ echo 'main(){}' | gcc -x c -S -o - - -pg | grep mcount
56 be (semi-)relevant.
[all …]
Duser_events.rst2 user_events: User-based Event Tracing
8 --------
10 that can be viewed via existing tools, such as ftrace and perf.
20 requires CAP_PERFMON due to the event persisting, otherwise -EPERM is returned.
23 tools that can read trace_events (such as ftrace and perf). The registration
36 -----------
44 /* Input: Size of the user_reg structure being used */
45 __u32 size;
50 /* Input: Enable size in bytes at address */
68 + size: This must be set to sizeof(struct user_reg).
[all …]
Dftrace.rst2 ftrace - Function Tracer
13 - Written for: 2.6.28-rc2
14 - Updated for: 3.10
15 - Updated for: 4.13 - Copyright 2017 VMware Inc. Steven Rostedt
16 - Converted to rst format - Changbin Du <changbin.du@intel.com>
19 ------------
21 Ftrace is an internal tracer designed to help out developers and
24 performance issues that take place outside of user-space.
26 Although ftrace is typically considered the function tracer, it
32 One of the most common uses of ftrace is the event tracing.
[all …]
Dstm.rst1 .. SPDX-License-Identifier: GPL-2.0
34 associated with it, located in "stp-policy" subsystem directory in
40 $ ls /config/stp-policy/dummy_stm.my-policy/user
42 $ cat /config/stp-policy/dummy_stm.my-policy/user/masters
44 $ cat /config/stp-policy/dummy_stm.my-policy/user/channels
70 catch-all entry "default" will be used, if it exists. This entry also
81 and have better control over the un-identified sources.
84 to userspace for zero-copy writing. One mappable page (in terms of
88 stm device's channel mmio region is 64 bytes and hardware page size is
99 For kernel-based trace sources, there is "stm_source" device
[all …]
Devents.rst24 ---------------------------------
59 ---------------------------
82 - 0 - all events this file affects are disabled
83 - 1 - all events this file affects are enabled
84 - X - there is a mixture of events enabled and disabled
85 - ? - this file does not affect any event
88 ---------------
92 trace_event=[event-list]
94 event-list is a comma separated list of events. See section 2.1 for event
97 3. Defining an event-enabled tracepoint
[all …]
Dkprobes.rst29 collect debugging and performance information non-disruptively. You
41 In the typical case, Kprobes-based instrumentation is packaged as
56 Kprobes -- e.g., the difference between a pre_handler and
62 -----------------------
74 Next, Kprobes single-steps its copy of the probed instruction.
75 (It would be simpler to single-step the actual instruction in place,
80 After the instruction is single-stepped, Kprobes executes the
85 -----------------------
105 -------------
114 is an arbitrary piece of code -- typically just a nop instruction.
[all …]
Dhistogram.rst27 [:sort=<field1[,field2,...]>][:size=#entries][:pause][:continue]
33 numeric fields - on an event hit, the value(s) will be added to a
35 in place of an explicit value field - this is simply a count of
45 useful for providing more fine-grained summaries of event data.
69 numeric fields are displayed as base-10 integers. This can be
76 .sym-offset display an address as a symbol and offset
80 .buckets=size display grouping of values rather than raw number
83 .graph display a bar-graph of a value
91 - only the 'hex' modifier can be used for values (because values
94 - the 'execname' modifier can only be used on a 'common_pid'. The
[all …]
Dhistogram-design.rst1 .. SPDX-License-Identifier: GPL-2.0
9 This document attempts to provide a description of how the ftrace
14 Note: All the ftrace histogram command examples assume the working
15 directory is the ftrace /tracing directory. For example::
20 generally be truncated - only enough to make the point is displayed.
35 can do with histograms - create one with a single key on a single
63 The hitcount value is a per-bucket value that's automatically
84 that such as the size, offset, type, and a hist_field_fn_t function,
85 which is used to grab the field's data from the ftrace event buffer
86 (in most cases - some hist_fields such as hitcount don't directly map
[all …]
/Documentation/devicetree/bindings/reserved-memory/
Dramoops.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 recovered after a reboot. This is a child-node of "/reserved-memory", and
16 as kernel log messages, or for optional ECC error-correction data. The total
17 size of these optional buffers must fit in the reserved region.
20 records. These records have a configurable size, with a size of 0 indicating
23 At least one of "record-size", "console-size", "ftrace-size", or "pmsg-size"
24 must be set non-zero, but are otherwise optional as listed below.
[all …]
/Documentation/admin-guide/
Dpstore-blk.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ------------
10 block device and non-block device before the system crashes. You can get
13 mount -t pstore pstore /sys/fs/pstore
17 ---------------------
27 Configurations for driver are all about block device and non-block device,
31 -----------------------
51 #. /dev/<disk_name><decimal> represents the device number of partition - device
53 #. /dev/<disk_name>p<decimal> - same as the above; this form is used when disk
60 #. PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF represents the unique id of
[all …]
Dramoops.rst9 ------------
17 ----------------
19 Ramoops uses a predefined memory area to store the dump. The start and size
23 * ``mem_size`` for the size. The memory size will be rounded down to a
60 ----------------------
68 the kernel to use only the first 128 MB of memory, and place ECC-protected
74 ``Documentation/devicetree/bindings/reserved-memory/ramoops.yaml``.
77 reserved-memory {
78 #address-cells = <2>;
79 #size-cells = <2>;
[all …]
Dkernel-parameters.txt16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
73 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]
Dkernel-parameters.rst3 The kernel's command-line parameters
12 The kernel parses parameters from the kernel command line up to "``--``";
16 Everything after "``--``" is passed as an argument to init.
32 log_buf_len=1M print-fatal-signals=1
36 log-buf-len=1M print_fatal_signals=1
38 Double-quotes can be used to protect spaces in values, e.g.::
43 ----------
52 <cpu number>-<cpu number>
57 <cpu number>,...,<cpu number>-<cpu number>
63 <cpu number>-<cpu number>:<used size>/<group size>
[all …]
/Documentation/arch/x86/
Dearlyprintk.rst1 .. SPDX-License-Identifier: GPL-2.0
7 Mini-HOWTO for using the earlyprintk=dbgp boot option with a
13 [host/target] <-------> [USB debug key] <-------> [client/console]
21 the lspci -vvv output::
23 # lspci -vvv
25 …roller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) (prog-if 20 [EHCI])
27 …Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisIN…
28 …Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- I…
31 Region 0: Memory at fe227000 (32-bit, non-prefetchable) [size=1K]
33 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
[all …]
/Documentation/admin-guide/pm/
Dintel_pstate.rst1 .. SPDX-License-Identifier: GPL-2.0
22 Documentation/admin-guide/pm/cpufreq.rst if you have not done that yet.]
24 For the processors supported by ``intel_pstate``, the P-state concept is broader
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
35 available frequencies due to the possible size of it, so the driver does not do
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
43 time the corresponding CPU is taken offline and need to be re-initialized when
47 only way to pass early-configuration-time parameters to it is via the kernel
66 -----------
[all …]
/Documentation/admin-guide/sysctl/
Dkernel.rst5 .. See scripts/check-sysctl-docs to keep this up to date
13 Documentation/admin-guide/sysctl/index.rst.
15 ------------------------------------------------------------------------------
39 If BSD-style process accounting is enabled these values control
71 The machine hardware name, the same output as ``uname -m``
129 Ctrl-Alt-Delete). Writing a value to this file which doesn't
130 correspond to a running process will result in ``-ESRCH``.
132 See also `ctrl-alt-del`_.
178 %c maximum size of core file by resource limit RLIMIT_CORE
219 ``core_sort_vma`` to 1, VMAs will be written from smallest size
[all …]
/Documentation/dev-tools/
Dkgdb.rst15 Kdb is simplistic shell-style interface which you can use on a system
22 kernel built-ins or in kernel modules if the code was built with
40 kgdb I/O modules compiled as built-ins or loadable kernel modules in the
46 - In order to enable compilation of kdb, you must first enable kgdb.
48 - The kgdb test compile options are described in the kgdb test suite
52 ------------------------------
55 :menuselection:`Kernel hacking --> Kernel debugging` and select
73 certain regions of the kernel's memory space as read-only. If kgdb
93 -----------------------------
108 If you want to use a PS/2-style keyboard with kdb, you would select
[all …]