Home
last modified time | relevance | path

Searched refs:tracing (Results 1 – 110 of 110) sorted by relevance

/linux-4.1.27/Documentation/trace/
Devents.txt11 using the event tracing infrastructure.
13 Not all tracepoints can be traced using the event tracing system;
15 tracing information is saved into the tracing buffer, and how the
16 tracing information should be printed.
24 The events which are available for tracing can be found in the file
25 /sys/kernel/debug/tracing/available_events.
28 to /sys/kernel/debug/tracing/set_event. For example:
30 # echo sched_wakeup >> /sys/kernel/debug/tracing/set_event
38 # echo '!sched_wakeup' >> /sys/kernel/debug/tracing/set_event
42 # echo > /sys/kernel/debug/tracing/set_event
[all …]
Dmmiotrace.txt1 In-kernel memory-mapped I/O tracing
8 MMIO tracing was originally developed by Intel around 2003 for their Fault
10 Jeff Muizelaar created a tool for tracing MMIO accesses with the Nouveau
26 supported, but tracing is unreliable and may miss events if more than one CPU
36 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
37 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
39 $ echo "X is up" > /sys/kernel/debug/tracing/trace_marker
40 $ echo nop > /sys/kernel/debug/tracing/current_tracer
54 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
57 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
[all …]
Dkprobetrace.txt19 /sys/kernel/debug/tracing/kprobe_events, and enable it via
20 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/enabled.
71 under tracing/events/kprobes/<EVENT>, at the directory you can see 'id',
90 /sys/kernel/debug/tracing/kprobe_profile.
100 …_sys_open dfd=%ax filename=%dx flags=%cx mode=+4($stack)' > /sys/kernel/debug/tracing/kprobe_events
109 echo 'r:myretprobe do_sys_open $retval' >> /sys/kernel/debug/tracing/kprobe_events
114 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/format.
116 cat /sys/kernel/debug/tracing/events/kprobes/myprobe/format
138 echo > /sys/kernel/debug/tracing/kprobe_events
148 Right after definition, each event is disabled by default. For tracing these
[all …]
Duprobetracer.txt14 /sys/kernel/debug/tracing/uprobe_events, and enable it via
15 /sys/kernel/debug/tracing/events/uprobes/<EVENT>/enabled.
64 /sys/kernel/debug/tracing/uprobe_profile.
73 echo 'p: /bin/bash:0x4245c0' > /sys/kernel/debug/tracing/uprobe_events
77 echo 'r: /bin/bash:0x4245c0' > /sys/kernel/debug/tracing/uprobe_events
81 echo '-:bash_0x4245c0' >> /sys/kernel/debug/tracing/uprobe_events
85 cat /sys/kernel/debug/tracing/uprobe_events
89 echo > /sys/kernel/debug/tracing/uprobe_events
94 # cd /sys/kernel/debug/tracing/
135 Right after definition, each event is disabled by default. For tracing these
[all …]
Devents-nmi.txt5 /sys/kernel/debug/tracing/events/nmi
32 cd /sys/kernel/debug/tracing/events/nmi/nmi_handler
38 $ cat /sys/kernel/debug/tracing/trace_pipe
Dftrace.txt22 is really a frame work of several assorted tracing utilities.
23 There's latency tracing to examine what occurs between interrupts
27 One of the most common uses of ftrace is the event tracing.
60 Any selected ftrace option will also create a directory called tracing
62 the ftrace directory (cd /sys/kernel/debug/tracing) and will only concentrate
64 the extended "/sys/kernel/debug/tracing" path name.
69 "tracing". This directory contains the control and output files
92 writing to the ring buffer, the tracing overhead may
103 file is meant to be streamed with live tracing.
165 If a process is performing the tracing, and the ring buffer
[all …]
Dcoresight.txt11 based SoC. It includes solutions for JTAG and HW assisted tracing. This
14 HW assisted tracing is becoming increasingly useful when dealing with systems
16 developed a HW assisted tracing solution by means of different components, each
17 being added to a design at synthesis time to cater to specific tracing needs.
22 path based on tracing scenarios as configured by users. From there the stream
88 the basic tracing functionality, enabling components such ETM/PTM, funnel,
212 comparator with "_stext" and "_etext", essentially tracing any instruction
Dtracepoint-analysis.txt11 tracing infrastructure.
20 the appropriate tracing options have been configured into the kernel. It is
29 All possible events are visible from /sys/kernel/debug/tracing/events. Simply
32 $ find /sys/kernel/debug/tracing/events -type d
62 $ for i in `find /sys/kernel/debug/tracing/events -name "enable" | grep mm_`; do echo 1 > $i; done
187 /sys/kernel/debug/tracing/trace_pipe in human-readable format although binary
Dftrace-design.txt8 Here we will cover the architecture pieces that the common function tracing
16 Ideally, everyone who wishes to retain performance while supporting tracing in
64 your system when tracing is disabled. So the start of the mcount function is
218 You need very few things to get the syscalls tracing in an arch.
225 in the ptrace syscalls tracing path.
342 is what helps us retain runtime performance when not tracing). The second is
Dtracepoints.txt31 They can be used for tracing and performance accounting.
62 In subsys/file.c (where the tracing statement must be added) :
Devents-power.txt4 The power tracing system captures events related to power transitions
Devents-kmem.txt3 The kmem tracing system captures events related to object and page allocation
/linux-4.1.27/Documentation/
Dirqflags-tracing.txt1 IRQ-flags state tracing
5 the "irq-flags tracing" feature "traces" hardirq and softirq state, in
19 state changes. But an architecture can be irq-flags-tracing enabled in a
28 irq-flags-tracing support:
35 irq-flags-tracing is spent in this state: look at the lockdep
38 lockdep complaint in the irq-flags-tracing functions arch support is
41 excluded from the irq-tracing [and lock validation] mechanism via
44 in general there is no risk from having an incomplete irq-flags-tracing
47 should be no crashes due to irq-tracing bugs. (except if the assembly
Dramoops.txt107 5. Persistent function tracing
109 Persistent function tracing might be useful for debugging software or hardware
D00-INDEX244 irqflags-tracing.txt
245 - how to use the irq-flags tracing feature.
342 oops-tracing.txt
443 - directory with info on tracing technologies within linux
Dworkqueue.txt371 The first one can be tracked using tracing:
373 $ echo workqueue:workqueue_queue_work > /sys/kernel/debug/tracing/set_event
374 $ cat /sys/kernel/debug/tracing/trace_pipe > out.txt
Dlocal_ops.txt27 coherent counters in NMI handlers. It is especially useful for tracing purposes
Dkmemleak.txt8 way similar to a tracing garbage collector
Dkernel-parameters.txt66 FTRACE Function tracing enabled.
1164 tracing directory.
1170 tracing directory.
1177 set_graph_function file in the debugfs tracing directory.
1183 set_graph_notrace file in the debugfs tracing directory.
3460 tracing directory. Note, this enables stack tracing
3644 [FTRACE] will set tracing buffer size on each cpu.
3657 /sys/kernel/debug/tracing/trace_options
3669 tracing ring buffer. This is useful for early boot up
3671 option for reading the tracing buffer or performing a
[all …]
Doops-tracing.txt143 Notes on Oops tracing with klogd:
Dkernel-per-CPU-kthreads.txt26 cd /sys/kernel/debug/tracing
Dkmemcheck.txt76 When function tracing is compiled in, gcc emits a call to another
Ddevices.txt2644 193 char Kernel event-tracing interface
2682 197 char OpenTNF tracing facility
/linux-4.1.27/Documentation/acpi/
Dmethod-tracing.txt7 The temporary debug_layer used when tracing the method.
11 The temporary debug_level used when tracing the method.
15 The status of the tracing feature.
24 Users can enable/disable this debug tracing feature by
/linux-4.1.27/tools/perf/util/
Dutil.c313 static void set_tracing_events_path(const char *tracing, const char *mountpoint) in set_tracing_events_path() argument
316 mountpoint, tracing, "events"); in set_tracing_events_path()
388 static char *tracing; in find_tracing_dir() local
393 return tracing; in find_tracing_dir()
403 if (asprintf(&tracing, "%s%s", debugfs, tracing_dir) < 0) in find_tracing_dir()
407 return tracing; in find_tracing_dir()
412 const char *tracing; in get_tracing_file() local
415 tracing = find_tracing_dir(); in get_tracing_file()
416 if (!tracing) in get_tracing_file()
419 if (asprintf(&file, "%s/%s", tracing, name) < 0) in get_tracing_file()
/linux-4.1.27/drivers/staging/ozwpan/
DTODO2 - Convert event tracing code to in-kernel tracing infrastructure
7 tracing.
/linux-4.1.27/kernel/trace/
DKconfig87 Adds a very slight overhead to tracing when enabled.
113 # be able to offer generic tracing facilities:
117 # PPC32 has no irqflags tracing support, but it can use most of the
120 # irqflags tracing for your architecture.
131 Enable the kernel tracing infrastructure.
146 tracing is enabled by the administrator. If it's runtime disabled
184 echo 0 > /sys/kernel/debug/tracing/tracing_max_latency
208 echo 0 > /sys/kernel/debug/tracing/tracing_max_latency
245 Allow tracing users to take snapshot of the current buffer using the
248 echo 1 > /sys/kernel/debug/tracing/snapshot
[all …]
/linux-4.1.27/drivers/char/mwave/
DREADME8 0x0001 mwavedd api tracing
9 0x0002 smapi api tracing
10 0x0004 3780i tracing
11 0x0008 tp3780i tracing
/linux-4.1.27/arch/s390/kernel/
Dhead64.S56 .quad 0 # cr9: tracing off
57 .quad 0 # cr10: tracing off
58 .quad 0 # cr11: tracing off
59 .quad 0 # cr12: tracing off
/linux-4.1.27/drivers/oprofile/
Dcpu_buffer.c79 b->tracing = 0; in alloc_cpu_buffers()
287 cpu_buf->tracing = 1; in oprofile_begin_trace()
292 cpu_buf->tracing = 0; in oprofile_end_trace()
423 if (!cpu_buf->tracing) in oprofile_add_trace()
438 cpu_buf->tracing = 0; in oprofile_add_trace()
Dcpu_buffer.h45 int tracing; member
/linux-4.1.27/drivers/hwtracing/coresight/
DKconfig58 which allows tracing the instructions that a processor is executing
59 This is primarily useful for instruction level tracing. Depending
60 the ETM version data tracing may also be available.
/linux-4.1.27/drivers/net/wireless/ath/ath10k/
DKconfig35 bool "Atheros ath10k tracing support"
39 Select this to ath10k use tracing infrastructure.
/linux-4.1.27/drivers/net/wireless/ath/wil6210/
DKconfig32 bool "wil6210 tracing support"
38 using the kernel tracing infrastructure. Select this
/linux-4.1.27/drivers/net/wireless/iwlwifi/
DKconfig105 This option will enable debug tracing output for the iwlwifi drivers
141 bool "iwlwifi device access tracing"
146 register with the ftrace framework for event tracing and dump
151 When tracing is not enabled, this option still has some
/linux-4.1.27/arch/m68k/ifpsp060/
Diskeleton.S90 | Linux/68k: commented out test for tracing
94 | tst.b (%sp) | is tracing enabled?
126 | no action associated with the "chk" exception. If tracing is enabled,
130 | Linux/68k: commented out test for tracing
134 | tst.b (%sp) | is tracing enabled?
/linux-4.1.27/drivers/net/wireless/ath/ath6kl/
DKconfig45 bool "Atheros ath6kl tracing support"
49 Select this to ath6kl use tracing infrastructure which, for
/linux-4.1.27/tools/testing/selftests/ftrace/
DREADME3 This is a collection of testcases for ftrace tracing feature in the Linux
29 * The working directory of the script is <debugfs>/tracing/.
Dftracetest91 TRACING_DIR=$DEBUGFS_DIR/tracing
/linux-4.1.27/drivers/net/wireless/brcm80211/
DKconfig72 bool "Broadcom device tracing"
78 issues. This option adds a small amount of overhead when tracing
/linux-4.1.27/Documentation/input/
Dappletouch.txt75 deactivates any debugging, 1 activates tracing of invalid samples, 2 activates
76 full tracing (each sample is being traced):
/linux-4.1.27/arch/arm/kernel/
Dentry-common.S36 ldr r1, [tsk, #TI_FLAGS] @ re-check for syscall tracing
194 ldr r10, [tsk, #TI_FLAGS] @ check for syscall tracing
197 tst r10, #_TIF_SYSCALL_WORK @ are we tracing syscalls?
/linux-4.1.27/arch/tile/
DKconfig.debug22 defined in arch/tile/kernel/hvglue.S. This allows tracing
/linux-4.1.27/Documentation/zh_CN/
Doops-tracing.txt1 Chinese translated version of Documentation/oops-tracing.txt
11 Documentation/oops-tracing.txt 的中文翻译
/linux-4.1.27/tools/perf/Documentation/
Dperf-lock.txt20 produces the file "perf.data" which contains tracing
Dperf-script-python.txt79 - we could enable every event under the tracing/events/syscalls
87 tracing/events/raw_syscalls. These are called for all syscalls; the
324 'perf list' and/or look in /sys/kernel/debug/tracing events for
456 (see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format):
Dperf-trace.txt127 When tracing pagefaults, the format of the trace is as follows:
Dexamples.txt221 in include/tracing/events/kmem.h.
Dperf-kvm.txt57 And this command produces a file which contains tracing results of kvm
Dperf-script-perl.txt58 (see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format):
Dperf-probe.txt111 space tracing. Can also be used with --funcs option.
/linux-4.1.27/drivers/net/wireless/ipw2x00/
DKconfig53 This option will enable debug tracing output for the IPW2100.
147 This option will enable low level debug tracing output for IPW2200.
181 This option will enable debug tracing output for the
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-etm3x5 Description: (RW) Enable/disable tracing on this specific trace entiry.
57 address to start tracing on, highly influenced by the
65 address to stop tracing on, highly influenced by the
149 context ID size and cycle accurate tracing. Driver specific
/linux-4.1.27/arch/mn10300/kernel/
Dentry.S132 # is there any work to be done other than syscall tracing?
148 # perform syscall entry tracing
164 # userspace resumption stub bypassing syscall exit tracing
/linux-4.1.27/arch/m32r/kernel/
Dentry.S151 ; userspace resumption stub bypassing syscall exit tracing
/linux-4.1.27/drivers/net/wireless/ath/
DKconfig29 bool "Atheros wireless tracing"
/linux-4.1.27/tools/vm/
Dslabinfo.c88 int tracing = 0; variable
658 if (tracing) in debug_opt_scan()
660 tracing = 1; in debug_opt_scan()
733 if (tracing && !s->trace) { in slab_debug()
739 if (!tracing && s->trace) in slab_debug()
/linux-4.1.27/arch/mips/kernel/
Dentry.S147 # other than syscall tracing?
Dscall64-64.S58 LONG_L t0, TI_FLAGS($28) # syscall tracing enabled?
Dscall64-n32.S51 LONG_L t0, TI_FLAGS($28) # syscall tracing enabled?
Dscall32-o32.S94 lw t0, TI_FLAGS($28) # syscall tracing enabled?
Dscall64-o32.S85 LONG_L t0, TI_FLAGS($28) # syscall tracing enabled?
/linux-4.1.27/drivers/net/wireless/ath/ath5k/
DKconfig50 using the kernel tracing infrastructure. Select this
/linux-4.1.27/arch/x86/
DKconfig.debug115 patching and dynamic kernel tracing - and they might also protect
162 allow to enable IOMMU leak tracing. Can be disabled at boot
180 bool "IOMMU leak tracing"
/linux-4.1.27/arch/x86/kernel/
Dentry_32.S324 # userspace resumption stub bypassing syscall exit tracing
608 # than syscall tracing?
645 # perform syscall exit tracing
657 # perform syscall exit tracing
/linux-4.1.27/lib/
DKconfig.kmemcheck17 This option enables tracing of dynamically allocated kernel memory
DKconfig.debug1090 either tracing or lock debugging.
1315 bool "Enable tracing for RCU"
1319 This option provides tracing in RCU which presents stats
1322 Say Y here if you want to enable RCU tracing
/linux-4.1.27/drivers/net/wireless/iwlegacy/
DKconfig70 This option will enable debug tracing output for the iwlegacy
/linux-4.1.27/
DREPORTING-BUGS90 report. Please read "Documentation/oops-tracing.txt" before posting your
116 resolved (see Documentation/oops-tracing.txt)
DREADME352 on making sense of the dump is in Documentation/oops-tracing.txt
/linux-4.1.27/arch/frv/kernel/
Dentry.S1135 # perform syscall entry tracing
1149 # perform syscall exit tracing
/linux-4.1.27/net/mac80211/
DKconfig113 runtime for tracing.
173 debug tracing output.
/linux-4.1.27/fs/reiserfs/
DKconfig53 reiserfs or tracing problems should say N.
/linux-4.1.27/arch/arm64/
DKconfig.debug65 patching and dynamic kernel tracing - and they might also protect
/linux-4.1.27/Documentation/video4linux/bttv/
DREADME.freeze25 Read Documentation/oops-tracing.txt to learn how to get any useful
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dcoresight.txt5 SoCs tracing needs. These trace components can generally be classified as
/linux-4.1.27/Documentation/vm/
Dpage_owner.txt13 Although we already have tracepoint for tracing page allocation/free,
Dslub.txt82 and tracing may only be enabled. The other options may cause the realignment
85 Careful with tracing: It may spew out lots of information and never stop if
/linux-4.1.27/arch/arc/kernel/
Dentry.S254 ; icause1 needs to be read early, before calling tracing, which
603 ; a tracing signal, tracer could have done a POKEUSR(CALLEE reg)
/linux-4.1.27/Documentation/infiniband/
Dipoib.txt76 to 'y', tracing messages are compiled into the driver. They are
/linux-4.1.27/Documentation/scsi/
Dadvansys.txt75 Enabling this option adds tracing functions to the driver and the
76 ability to set a driver tracing level at boot time. This option is
DBusLogic.txt496 The "TraceProbe" option enables tracing of Host Adapter Probing.
500 The "TraceHardwareReset" option enables tracing of Host Adapter Hardware
505 The "TraceConfiguration" option enables tracing of Host Adapter
510 The "TraceErrors" option enables tracing of SCSI Commands that return an
/linux-4.1.27/tools/virtio/virtio-trace/
DREADME98 # echo 1 > /sys/kernel/debug/tracing/events/sched/enable
/linux-4.1.27/Documentation/frv/
Dgdbstub.txt48 and wait for GDB to connect. This allows you to start tracing right from
/linux-4.1.27/Documentation/RCU/
Dstallwarn.txt249 and with RCU's event tracing. For information on RCU's event tracing,
/linux-4.1.27/arch/unicore32/kernel/
Dentry.S624 ldw ip, [tsk+], #TI_FLAGS @ check for syscall tracing
625 cand.a ip, #_TIF_SYSCALL_TRACE @ are we tracing syscalls?
/linux-4.1.27/Documentation/filesystems/
D9p.txt93 0x800 = display fscache tracing debug
Drelay.txt302 as when doing early tracing in the kernel, before the VFS is up. In these
485 discussions on tracing involving the following:
Dxfs-delayed-logging-design.txt150 3. Supply sufficient new tracing infrastructure to be able to debug
Dproc.txt220 TracerPid PID of process tracing this process (0 if not)
/linux-4.1.27/arch/
DKconfig85 passing of pt_regs to function tracing, then kprobes can
86 optimize on top of function tracing.
/linux-4.1.27/arch/score/kernel/
Dentry.S312 # other than syscall tracing?
/linux-4.1.27/arch/c6x/kernel/
Dentry.S218 ;; tracing returns (possibly new) syscall number
/linux-4.1.27/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt2829 it later by sending the tracing thread a SIGUSR1. The first line of
2831 tracing thread pid = 20093
2911 That will strace only the main UML thread, the tracing thread, which
3060 $14 = {extern_pid = 1980, tracing = 0, want_tracing = 0, forking = 0,
4133 The less common and more painful case is when the tracing thread
4135 needs a healthy tracing thread in order to work. The first thing to
4136 do is get a backtrace from the tracing thread. This is done by
4138 pid. You can figure out the tracing thread pid by looking at the
4142 tracing thread pid = 15851
4151 jdike 15851 4.5 0.4 132568 1104 pts/0 S 21:34 0:05 ./linux [(tracing thread)]
[all …]
/linux-4.1.27/Documentation/s390/
DDebugging390.txt1024 The most common ones you will normally be tracing for is
1042 If you have a complex tracing situation where you wish to wait for instance
1043 till a driver is open before you start tracing IO, but know in your
1116 e.g. consider tracing an open syscall
1206 Stack tracing under VM
1460 Now we are ready to go on with IO tracing commands under VM
1493 A good trick is tracing all the IO's and CCWS and spooling them into the reader
2130 CMS Help on tracing commands.
/linux-4.1.27/arch/cris/arch-v32/kernel/
Dentry.S261 ;; perform syscall exit tracing if needed.
/linux-4.1.27/arch/blackfin/
DKconfig.debug193 Say Y here to disable hardware tracing in some known "jumpy" pieces
/linux-4.1.27/drivers/media/usb/pwc/
Dphilips.txt214 you want to turn the initialization and probing tracing off, set trace=0.
/linux-4.1.27/kernel/power/
DKconfig209 bool "Suspend/resume event tracing"
/linux-4.1.27/Documentation/x86/x86_64/
Dboot-options.txt223 leak Turn on simple iommu leak tracing (only when
/linux-4.1.27/Documentation/sound/alsa/
DHD-Audio.txt611 # echo 1 > /sys/kernel/debug/tracing/events/hda/enable
614 /sys/kernel/debug/tracing/trace file. For example, when you want to
617 # cat /sys/kernel/debug/tracing/trace
/linux-4.1.27/arch/cris/arch-v10/kernel/
Dentry.S225 ;; perform syscall exit tracing if needed
/linux-4.1.27/Documentation/filesystems/cifs/
DREADME687 These experimental features and tracing can be enabled by changing flags in
690 tracing to the kernel message log type:
700 and setting it to seven enables all three. Finally, tracing
/linux-4.1.27/tools/perf/
Ddesign.txt146 /debug/tracing/events/*/*/id
/linux-4.1.27/arch/x86/math-emu/
DREADME201 disabled during tracing ]
/linux-4.1.27/Documentation/networking/
Dfilter.txt819 tracing filters may do to maintain counters of events, for example. Register R9
1084 Socket filters may let programs to call one set of functions, whereas tracing
/linux-4.1.27/Documentation/security/
Dcredentials.txt102 signalling and tracing tasks.
/linux-4.1.27/net/ipv4/
DKconfig281 an aid in tracing the packets to their actual source and should not
/linux-4.1.27/arch/arm/
DKconfig.debug1593 patching and dynamic kernel tracing - and they might also protect
/linux-4.1.27/init/
DKconfig660 This option provides tracing for the TREE_RCU and