- On Jul 14, 2022, at 9:10 AM, Norbert Lange nolang...@gmail.com wrote:
> Hello Mathieu,
>
> Am Do., 20. Mai 2021 um 16:16 Uhr schrieb Mathieu Desnoyers
> :
>>
>> - On May 20, 2021, at 9:42 AM, Norbert Lange nolang...@gmail.com wrote:
>>
>> > Am Do., 20. Mai 2021 um 15:28 Uhr schrieb Math
- On Jul 15, 2022, at 9:19 AM, Pennese Marco via lttng-dev
wrote:
> Hi,
> I’m trying to use LTTng on a Red Hat Enterprise Linux 7.9 (with the real time
> kernel patch).
> I installed LTTng on the machine following the EfficiOS guide linked by lttng
> official website.
> In my configurati
Support two common cases, one being that the resulting message is
small enough to fit into a on-stack buffer.
The seconds being the common 'printf("%s", "Message")' scheme.
Unfortunately, iterating a va_list is destructive,
so it has to be copied before calling vprintf.
The implementation was mov
Eagerly register the thread, and avoid taking mutex during the
first tracepoint.
Signed-off-by: Norbert Lange
---
src/lib/lttng-ust/lttng-ust-comm.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/lib/lttng-ust/lttng-ust-comm.c
b/src/lib/lttng-ust/lttng-ust-comm.c
index ba0bd985..3ff6
Modify all relevant *_alloc_tls functions so that they take an
argument for 'init'. Setting this to 'true' will read
the actual context value and store it into a thread local
cache.
The function 'lttng_ust_init_thread' will use this to
precalculate context values. Tracepoints can then avoid
system