/openbmc/linux/kernel/trace/ |
H A D | Kconfig | 139 Adds a very slight overhead to tracing when enabled. 174 # be able to offer generic tracing facilities: 187 Enable the kernel tracing infrastructure. 246 bool "enable/disable function tracing dynamically" 260 See the files in /sys/kernel/tracing: 504 bool "Memory mapped IO tracing" 540 echo 1 > /sys/kernel/tracing/snapshot 599 /sys/kernel/tracing/trace_stat/branch_annotated 612 /sys/kernel/tracing/trace_stat/branch_all 644 bool "Support for tracing block IO actions" [all …]
|
/openbmc/linux/arch/powerpc/platforms/powernv/ |
H A D | Kconfig | 30 bool "Enable runtime allocation of RAM for tracing" 34 for hardware tracing.
|
/openbmc/openbmc/poky/documentation/profile-manual/ |
H A D | arch.rst | 11 architecture' for what seems to be a random collection of tracing tools 12 that together make up the Linux tracing and profiling space. The fact
|
H A D | usage.rst | 10 This chapter presents basic usage examples for each of the tracing 16 The perf tool is the profiling and tracing tool that comes bundled 890 ``-a`` flag (press ``Ctrl-C`` to stop tracing):: 1215 ``/sys/kernel/debug/tracing`` on a Yocto system are:: 1217 root@sugarbay:/sys/kernel/debug/tracing# ls 1232 tracing options, and yet others actually contain the tracing output when 1462 root@sugarbay:/sys/kernel/debug/tracing# cd events 1772 ``/sys/kernel/debug/tracing/README``. 2059 tracing. 2237 efficient software tracing. [all …]
|
H A D | intro.rst | 10 Yocto Project bundles a number of tracing and profiling tools --- this manual 21 useful tracing and profiling idioms along with their application (as 49 the tracing and profiling tools will be included in non-sdk images as well e.g.::
|
/openbmc/linux/drivers/net/wireless/ath/ath12k/ |
H A D | Kconfig | 28 bool "ath12k tracing support" 31 Enable ath12k tracing infrastructure.
|
/openbmc/linux/Documentation/trace/ |
H A D | ftrace.rst | 60 mount -t tracefs nodev /sys/kernel/tracing 65 ln -s /sys/kernel/tracing /tracing 74 /sys/kernel/debug/tracing 85 "/sys/kernel/tracing" path name. 489 Usual clocks for tracing:: 658 Usual timestamp modes for tracing: 1288 use function graph tracing instead of function tracing. 1937 Without function tracing:: 2174 Latency tracing and events 2377 Single thread tracing [all …]
|
H A D | osnoise-tracer.rst | 47 tracing system (generally mounted at /sys/kernel/tracing). 51 [root@f32 ~]# cd /sys/kernel/tracing/ 52 [root@f32 tracing]# echo osnoise > current_tracer 56 [root@f32 tracing]# cat trace 103 - osnoise/stop_tracing_us: stop the system tracing if a single noise 106 - osnoise/stop_tracing_total_us: stop the system tracing if total noise 173 approach: measuring thread and tracing.
|
H A D | user_events.rst | 14 /sys/kernel/tracing/user_events_status and can both register and write 15 data out via /sys/kernel/tracing/user_events_data. 22 on the /sys/kernel/tracing/user_events_data file. 33 /sys/kernel/tracing/user_events_data file. The command to issue is 91 events need to use /sys/kernel/tracing/events/user_events/[name]/enable 135 /sys/kernel/tracing/user_events_data file. The command to issue is 149 be disabled via ioctl() out to the /sys/kernel/tracing/user_events_data file.
|
/openbmc/linux/tools/lib/api/fs/ |
H A D | tracing_path.c | 18 static void __tracing_path_set(const char *tracing, const char *mountpoint) in __tracing_path_set() argument 21 mountpoint, tracing); in __tracing_path_set()
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-coresight-devices-etm4x | 5 Description: (RW) Enable/disable tracing on this specific trace entiry. 22 available for tracing. 29 available for tracing. 36 tracing. 49 available for tracing. 56 for tracing. 70 available for tracing. 77 are available for tracing. 92 context ID tracing. 149 tracing is enabled for the corresponding exception level. [all …]
|
/openbmc/qemu/docs/tools/ |
H A D | qemu-trace-stap.rst | 13 The ``qemu-trace-stap`` program facilitates tracing of the execution 76 capable of tracing all known QEMU probes concurrently without overflowing 90 Restrict the tracing session so that it only triggers for the process 108 tracing environment:
|
/openbmc/openbmc/meta-security/recipes-security/krill/ |
H A D | krill-crates.inc | 233 crate://crates.io/tracing/0.1.35;name=tracing-0.1.35 \ 234 crate://crates.io/tracing-attributes/0.1.22;name=tracing-attributes-0.1.22 \ 235 crate://crates.io/tracing-core/0.1.28;name=tracing-core-0.1.28 \ 236 crate://crates.io/tracing-log/0.1.3;name=tracing-log-0.1.3 \ 237 crate://crates.io/tracing-serde/0.1.3;name=tracing-serde-0.1.3 \ 238 crate://crates.io/tracing-subscriber/0.2.25;name=tracing-subscriber-0.2.25 \ 507 SRC_URI[tracing-0.1.35.sha256sum] = "a400e31aa60b9d44a52a8ee0343b5b18566b03a8321e0d321f695cf56e9401… 508 SRC_URI[tracing-attributes-0.1.22.sha256sum] = "11c75893af559bc8e10716548bdef5cb2b983f8e637db9d0e15… 509 SRC_URI[tracing-core-0.1.28.sha256sum] = "7b7358be39f2f274f322d2aaed611acc57f382e8eb1e5b48cb9ae3093… 510 SRC_URI[tracing-log-0.1.3.sha256sum] = "78ddad33d2d10b1ed7eb9d1f518a5674713876e97e5bb9b7345a7984fbb… [all …]
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | visl.rst | 18 debugfs interface. This is in many ways similar to the tracing 40 frames where dprintk is activated. This only controls the dprintk tracing on a 81 $ ls /sys/kernel/debug/tracing/events/ | grep visl 93 $ echo 1 > /sys/kernel/debug/tracing/events/visl_hevc_controls/v4l2_ctrl_hevc_sps/enable 99 $ cat /sys/kernel/debug/tracing/trace
|
/openbmc/linux/drivers/net/wireless/ath/ath11k/ |
H A D | Kconfig | 47 bool "ath11k tracing support" 50 Select this to use ath11k tracing infrastructure.
|
/openbmc/linux/drivers/net/wireless/broadcom/brcm80211/ |
H A D | Kconfig | 28 bool "Broadcom device tracing" 34 issues. This option adds a small amount of overhead when tracing
|
/openbmc/linux/tools/perf/Documentation/ |
H A D | perf-ftrace.txt | 20 single thread tracing currently and just reads trace_pipe in text and then 72 Time (ms) to wait before starting tracing after program start. 76 Set the size of per-cpu tracing buffer, <size> is expected to 115 for the function_graph tracer only and disables tracing for function
|
/openbmc/linux/tools/testing/selftests/rcutorture/configs/rcuscale/ |
H A D | TRACE01.boot | 1 rcuscale.scale_type=tasks-tracing
|
/openbmc/linux/tools/testing/selftests/rcutorture/configs/rcu/ |
H A D | TRACE01.boot | 1 rcutorture.torture_type=tasks-tracing
|
H A D | TRACE02.boot | 1 rcutorture.torture_type=tasks-tracing
|
/openbmc/linux/Documentation/core-api/irq/ |
H A D | index.rst | 11 irqflags-tracing
|
/openbmc/linux/drivers/net/ethernet/sfc/siena/ |
H A D | Kconfig | 42 This enables support for tracing of MCDI (Management-Controller-to- 44 driver/firmware interaction. The tracing is actually enabled by
|
/openbmc/qemu/hw/alpha/ |
H A D | trace-events | 1 # See docs/devel/tracing.rst for syntax documentation.
|
/openbmc/qemu/hw/block/dataplane/ |
H A D | trace-events | 1 # See docs/devel/tracing.rst for syntax documentation.
|
/openbmc/qemu/ebpf/ |
H A D | trace-events | 1 # See docs/devel/tracing.rst for syntax documentation.
|