[lttng-dev] [PATCH lttng-tools] fix: Re-add link to urcu-bp for _LGPL_SOURCE tests

2019-11-05 Thread Michael Jeanson
Tests with tracepoints defined with _LGPL_SOURCE require to be explicitly linked against urcu-bp. Signed-off-by: Michael Jeanson --- tests/regression/ust/multi-session/Makefile.am | 2 +- tests/utils/testapp/gen-ust-events/Makefile.am | 2 +- tests/utils/testapp/gen-ust-nevents-str/Mak

Re: [lttng-dev] [PATCH lttng-tools] fix: Re-add link to urcu-bp for _LGPL_SOURCE tests

2019-11-05 Thread Jérémie Galarneau
Merged in master. Thanks! Jérémie On Tue, Nov 05, 2019 at 11:30:24AM -0500, Michael Jeanson wrote: > Tests with tracepoints defined with _LGPL_SOURCE require to be > explicitly linked against urcu-bp. > > Signed-off-by: Michael Jeanson > --- > tests/regression/ust/multi-session/Makefile.am

[lttng-dev] [RFC PATCH lttng-tools 2/3] align.h: Implement ALIGN_FLOOR macro

2019-11-05 Thread Mathieu Desnoyers
Implement the ALIGN_FLOOR macro which aligns the given value to the previous alignment boundary, or keeps the value as-is if it is already aligned. Signed-off-by: Mathieu Desnoyers --- src/common/align.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/src/common/align.h b/src/common/al

[lttng-dev] [RFC PATCH lttng-tools 3/3] Fix: consumerd: use packet sequence number for rotation position

2019-11-05 Thread Mathieu Desnoyers
Refer to "Fix: relayd: use packet sequence number for rotation position" for context of this change. This commit introduces the changes required in the consumerd. Some notable points related to this commit: - The per-stream rotation position within the consumerd is now the very start of the fi

[lttng-dev] [RFC PATCH lttng-tools 1/3] Fix: relayd: use packet sequence number for rotation position

2019-11-05 Thread Mathieu Desnoyers
The "network" sequence number (net_seq_num) is a 64-bit sequence number tagging each packet sent over the network. The net_seq_num increments monotonically (+1) for each packet sent from consumer daemon to relay daemon, on a per-stream basis. It is tagged by the consumer daemon when sending a trace

Re: [lttng-dev] 回复:Re: 回复:Re: 回复:Re: Pros and Cons of LTTng

2019-11-05 Thread 杨海
Thanks Jonathan. Regarding to the CI MTTR/MTTF test results, it varies from time to time, and on master/stable branches.  1. it monitors new Linux kernels, so the CI job may use newer kernel version than months ago? 2. What would be the criteria of MTBF here? MTTRLast 7 Days0 ms Last 30 Days12