Home
last modified time | relevance | path

Searched full:perf (Results 1 – 18 of 18) sorted by relevance

/Zephyr-latest/samples/subsys/profiling/perf/
DREADME.rst1 .. zephyr:code-sample:: profiling-perf
2 :name: Perf tool
4 Send perf samples to the host with console support
6 This application can be used to understand how to use the :ref:`profiling-perf`
12 The Perf tool is currently implemented only for RISC-V and x86_64 architectures.
20 :zephyr-app: samples/subsys/profiling/perf
29 uart:~$ perf record <duration> <frequency>
33 * Wait for the completion message ``perf done!``, or ``perf buf override!`` if
34 the perf buffer size is smaller than required.
36 * Print the samples captured by perf in the terminal with the shell command:
[all …]
Dsample.yaml2 description: Sample, that can be used for testing profiling perf tool
3 name: perf sample
6 sample.perf:
8 - perf
DCMakeLists.txt8 project(perf) project
/Zephyr-latest/doc/services/profiling/
Dperf.rst1 .. _profiling-perf:
3 Perf chapter
6 Perf is a profiler tool based on stack tracing. It can be used for lightweight profiling
12 The ``perf record`` shell command starts a timer with the perf tracer function.
13 Timers are driven by interrupts, so the perf tracer function is called during an interruption.
15 structure before calling the interrupt handler. Thus, the perf trace function makes stack traces by
28 the ``perf`` command to the shell.
30 * :kconfig:option:`CONFIG_PROFILING_PERF_BUFFER_SIZE`: Sets the size of the perf buffer
36 Refer to the :zephyr:code-sample:`profiling-perf` sample for an example of how to use the perf tool.
Dindex.rst11 perf.rst
/Zephyr-latest/samples/subsys/profiling/perf/pytest/
Dtest_perf.py19 logger.info('send "perf record 200 99" command')
20 lines = shell.exec_command('perf record 200 99')
21 assert 'Enabled perf' in lines, 'expected response not found'
22 lines = dut.readlines_until(regex='.*Perf done!', print_output=True)
25 logger.info('send "perf printbuf" command')
26 lines = shell.exec_command('perf printbuf')
28 match = re.match(r"Perf buf length (\d+)", lines[0])
/Zephyr-latest/subsys/profiling/perf/
Dperf.c67 shell_error(perf_data_ptr->sh, "Perf buf overflow!"); in perf_dwork_handler()
69 shell_print(perf_data_ptr->sh, "Perf done!"); in perf_dwork_handler()
76 shell_warn(sh, "Perf is running"); in cmd_perf_record()
81 shell_warn(sh, "Perf buffer is full"); in cmd_perf_record()
95 shell_print(sh, "Enabled perf"); in cmd_perf_record()
104 shell_warn(sh, "Perf is running"); in cmd_perf_clear()
107 shell_print(sh, "Perf buffer cleared"); in cmd_perf_clear()
119 shell_print(sh, "Perf is running"); in cmd_perf_info()
122 shell_print(sh, "Perf buf: %zu/%d %s", perf_data.idx, CONFIG_PROFILING_PERF_BUFFER_SIZE, in cmd_perf_info()
131 shell_warn(sh, "Perf is running"); in cmd_perf_print()
[all …]
DKconfig6 bool "Perf support"
11 Enable perf shell command.
16 int "Perf buffer size"
19 Size of buffer used by perf to save stack trace samples.
DCMakeLists.txt10 perf.c
/Zephyr-latest/samples/net/sockets/http_server/
DREADME.rst211 We can use ``perf`` to collect statistics about the CPU usage of our server
216 $ sudo perf stat -p <pid_of_server>
218 ``perf stat`` will then start monitoring our server. We can let it run while
220 stop ``perf stat``, which will print a summary of the performance statistics.
225 ``perf record`` and ``perf report`` can be used together to identify the
230 $ sudo perf record -g -p <pid_of_server> -o perf.data
237 $ sudo perf report -i perf.data
239 After generating a file named ``perf.data`` which contains the profiling data,
244 To do this, we need to convert the ``perf.data`` to a format that ``FlameGraph``
249 $ sudo perf script | ~/FlameGraph/stackcollapse-perf.pl > out.perf-folded
[all …]
/Zephyr-latest/subsys/profiling/
DKconfig8 Enable profiling tools, such as perf
12 source "subsys/profiling/perf/Kconfig"
DCMakeLists.txt5 add_subdirectory_ifdef(CONFIG_PROFILING_PERF perf)
/Zephyr-latest/scripts/profiling/
Dstackcollapse.py11 This translate stack samples captured by perf subsystem into format
16 ./script/perf/stackcollapse.py <file with perf printbuf output> <ELF file>
63 assert int(re.match(r"Perf buf length (\d+)", lines[0]).group(1)) == len(lines) - 1
/Zephyr-latest/drivers/sensor/st/iis2dlpc/
Diis2dlpc.h37 /* Acc Gain value in ug/LSB in High Perf mode */
/Zephyr-latest/drivers/sensor/st/lis2dw12/
Dlis2dw12.h46 /* Acc Gain value in ug/LSB in High Perf mode */
/Zephyr-latest/
DMAINTAINERS.yml843 "Debug: Profiling: Perf":
846 - doc/services/profiling/perf.rst
847 - samples/subsys/profiling/perf/
849 - subsys/profiling/perf/
851 - "area: Profiling / Perf"
853 - debug.profiling.perf
D.ruff-excludes.toml1475 "./samples/subsys/profiling/perf/pytest/test_perf.py",
/Zephyr-latest/drivers/flash/
Dspi_nor.c66 /* MXICY Low-power/high perf mode is second bit in configuration register 2 */
740 /* Low-power/high perf mode is second bit in configuration register 2 */ in mxicy_configure()