OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/subsys/tracing/sysview/tracing_sysview_syscall.h

20 lines
499 B
C
Raw Normal View History

tracing: Automatic syscall tracing When generating syscall wrappers, call a tracing macro with the id, name, and all parameters of the syscall as params when entering and leaving the syscall. This can be disabled in certain call sites by defining DISABLE_SYSCALL_TRACING which is useful for certain tracing implementations which require syscalls themselves to work. Notably some syscalls *cannot* be automatically traced this way and headers where exclusions are set are in the gen_syscall.py as notracing. Includes a systemview and test format implementation. Tested with systemview, usb, and uart backends with the string formatter using the tracing sample app. Debugging the trace wrapper can be aided by setting the TRACE_DIAGNOSTIC env var and rebuilding from scratch, a warning is issued for every instance a syscall is traced. Automatically generating a name mapping for SYSVIEW_Zephyr.txt is a future item as is documenting how to capture and use the tracing data generated. Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
2021-10-14 01:16:39 +08:00
/*
* Copyright (c) 2021 Intel Corporation
*
* SPDX-License-Identifier: Apache-2.0
*/
#ifndef ZEPHYR_TRACING_SYSVIEW_SYSCALL_H_
#define ZEPHYR_TRACING_SYSVIEW_SYSCALL_H_
#include <SEGGER_SYSVIEW.h>
#include <tracing_sysview_ids.h>
tracing: segger-sysview: fix display formatting Fixes several minor display errors in the Segger SystemView output: * Off-by-one error in some trace ids. * Add missing syscall trace id. * Displays easier to read syscall function names. * Fixes syntax error in k_timer_start output. Signed-off-by: Florian Grandel <fgrandel@code-for-humans.de>
2023-08-03 07:18:20 +08:00
#define sys_port_trace_syscall_enter(id, name, ...) \
SEGGER_SYSVIEW_RecordString(TID_SYSCALL, (const char *)#name)
tracing: Automatic syscall tracing When generating syscall wrappers, call a tracing macro with the id, name, and all parameters of the syscall as params when entering and leaving the syscall. This can be disabled in certain call sites by defining DISABLE_SYSCALL_TRACING which is useful for certain tracing implementations which require syscalls themselves to work. Notably some syscalls *cannot* be automatically traced this way and headers where exclusions are set are in the gen_syscall.py as notracing. Includes a systemview and test format implementation. Tested with systemview, usb, and uart backends with the string formatter using the tracing sample app. Debugging the trace wrapper can be aided by setting the TRACE_DIAGNOSTIC env var and rebuilding from scratch, a warning is issued for every instance a syscall is traced. Automatically generating a name mapping for SYSVIEW_Zephyr.txt is a future item as is documenting how to capture and use the tracing data generated. Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
2021-10-14 01:16:39 +08:00
tracing: segger-sysview: fix display formatting Fixes several minor display errors in the Segger SystemView output: * Off-by-one error in some trace ids. * Add missing syscall trace id. * Displays easier to read syscall function names. * Fixes syntax error in k_timer_start output. Signed-off-by: Florian Grandel <fgrandel@code-for-humans.de>
2023-08-03 07:18:20 +08:00
#define sys_port_trace_syscall_exit(id, name, ...) \
SEGGER_SYSVIEW_RecordEndCall(TID_SYSCALL)
tracing: Automatic syscall tracing When generating syscall wrappers, call a tracing macro with the id, name, and all parameters of the syscall as params when entering and leaving the syscall. This can be disabled in certain call sites by defining DISABLE_SYSCALL_TRACING which is useful for certain tracing implementations which require syscalls themselves to work. Notably some syscalls *cannot* be automatically traced this way and headers where exclusions are set are in the gen_syscall.py as notracing. Includes a systemview and test format implementation. Tested with systemview, usb, and uart backends with the string formatter using the tracing sample app. Debugging the trace wrapper can be aided by setting the TRACE_DIAGNOSTIC env var and rebuilding from scratch, a warning is issued for every instance a syscall is traced. Automatically generating a name mapping for SYSVIEW_Zephyr.txt is a future item as is documenting how to capture and use the tracing data generated. Signed-off-by: Tom Burdick <thomas.burdick@intel.com>
2021-10-14 01:16:39 +08:00
#endif /* ZEPHYR_TRACING_SYSVIEW_SYSCALL_H_ */