Hi Michael/everyone else,
Indeed the above does seem to resolve the issue. Thanks for looking into
this!
Cheers,
Sean
On Wed, Mar 2, 2016 at 5:45 PM, Michael Jeanson
wrote:
> Hi Sean,
>
> As mentioned by Mathieu this is caused by the docker default seccomp
> profile
> blocking the "restart_sy
- On Mar 10, 2016, at 5:59 PM, Jeffrey Chen wrote:
> Thanks, Mathieu.
> Yes, the fix works as a workaround. This is also the same workaround we have
> now.
> It seems the problem is due to a race condition, that it checked whether "
> tracepoint_dlopen.rcu_read_lock_sym_bp " is not NULL. I
Thanks, Mathieu.
Yes, the fix works as a workaround. This is also the same workaround we have
now.
It seems the problem is due to a race condition, that it checked whether
"tracepoint_dlopen.rcu_read_lock_sym_bp" is not NULL. If not NULL, it calls to
that. But, at this moment, memset cleared
- On Mar 10, 2016, at 9:44 AM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> Calling this function from an instrumented program allows disabling
> tracepoint destructors. This allows threads to continue calling
> tracepoint code even after the tracepoint destructors have run. This
Merged in master and stable-2.7, thanks!
Jérémie
On Thu, Mar 10, 2016 at 11:13 AM, Mathieu Desnoyers
wrote:
> Ensure that SIGKILL being received only by some consumer processes don't
> trigger clean shutdown of other consumer processes (due to hang up of
> communication FD by the session daemon)
- On Mar 10, 2016, at 3:33 PM, Yuxin Ren r...@gwmail.gwu.edu wrote:
> Thank you for your reply.
>
> I want to generally understand how to apply urcu to real time systems.
> I know real time system focus on predictability on both timing and
> memory consumption.
> So how does real time urcu su
Thank you for your reply.
I want to generally understand how to apply urcu to real time systems.
I know real time system focus on predictability on both timing and
memory consumption.
So how does real time urcu support predictability?
Could you provide me some papers, documents or any materials ab
Bug introduced in commit 2001793c1141e89b34e70efb28b27ec0cc8e6d47
The type and config fields of the lttng_event_perf_counter_ctx member of
lttng_event_context union would always be set to zero.
Signed-off-by: Jonathan Rajotte
---
src/lib/lttng-ctl/lttng-ctl.c | 12 +---
1 file changed,
Hi, folks.
I've been making tools to work with lttng-ust in the ruby ecosystem,
and I've just put some of the results of this work on github.
First, I've instrumented the ruby interpreter with lttng tracepoints,
which can be built with --enable-lttng and currently exist alongside
the existing dtr
Hi Jeffrey,
I CC'd your @live.com address on the RFC patch. Please let me know if the
approach
is OK with you (and try it out).
See:
https://lists.lttng.org/pipermail/lttng-dev/2016-March/025608.html
Thanks,
Mathieu
- On Mar 10, 2016, at 1:35 PM, Jeffrey Chen wrote:
> Thanks Mat
Real-time and embedded systems is an important current focus for the LTTng
toolchain research. Do you have specific needs for userspace RCU?
- Mail original -
> Hi,
>
> Is there any work or research about Userspace RCU on real time or
> embedded systems?
> Any information is welcome.
>
Thanks Mathieu.
Is there a plan at LTTng side to fix this issue? If so, we could wait for the
fix. If not, we will have to workaround the problem for now (probably by
applying your fix ourselves). Thanks.
From: Mathieu Desnoyers
Sent: Tuesday, March 8, 2016 6
Hi,
Is there any work or research about Userspace RCU on real time or
embedded systems?
Any information is welcome.
Thanks a lot!
Yuxin
___
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Merged in master, stable-2.7 and stable-2.6. Thanks!
Jérémie
On Tue, Mar 8, 2016 at 5:37 PM, Jonathan Rajotte
wrote:
> Sets the default lttng-sessiond path to /bin/true to prevent the spawning
> of a daemonized sessiond. This is necessary since 'lttng create' will spawn
> its own sessiond if non
Ensure that SIGKILL being received only by some consumer processes don't
trigger clean shutdown of other consumer processes (due to hang up of
communication FD by the session daemon).
Fix this by invoking a SIGSTOP on both sessiond and consumerd, and wait
until we see those process state change to
Calling this function from an instrumented program allows disabling
tracepoint destructors. This allows threads to continue calling
tracepoint code even after the tracepoint destructors have run. This is
needed for applications that exit without joining all their threads.
Signed-off-by: Mathieu De
16 matches
Mail list logo
