Done. Bug #776: http://bugs.lttng.org/issues/776
Amit Margalit
IBM XIV - Storage Reinvented
XIV-NAS Development Team
Tel. 03-689-7774
Fax. 03-689-7230
From: Jérémie Galarneau
To: Amit Margalit/Israel/IBM@IBMIL
Cc: lttng-dev
Date: 04/02/2014 05:47 PM
Subject:Re: [lttng-dev]
Hi,dev
In lttng-modules-2.3.0/lttng-syscalls.c :
ret = kabi_2635_tracepoint_probe_register("sys_enter",
(void *) syscall_entry_probe, chan);
ret = kabi_2635_tracepoint_probe_register("sys_exit",
(void *) __event_probe__exit_syscal
Hi LTTng'ers,
I've asked briefly for the configurable probes feature at the Tracing summit,
here is an RFC how we could implement it.
Why I want to have this feature:
Currently the LTTng probes that are loaded when a session is created are defined
in a static list. If the user wants to change the
Module loading (and unloading) is identical for control and data modules
so use common funtions to avoid code duplication.
Signed-off-by: Jan Glauber
---
src/bin/lttng-sessiond/modprobe.c | 109 -
1 file changed, 34 insertions(+), 75 deletions(-)
diff --git
Move all control modules to the control list and make a seperate
probes list.
Signed-off-by: Jan Glauber
---
src/bin/lttng-sessiond/modprobe.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/src/bin/lttng-sessiond/modprobe.c
b/src/bin/lttng-sessi
Remove the per module required parameter by adding another list
for optional core modules, so we have:
- required core modules
- optional core modules
- optional probe modules
Signed-off-by: Jan Glauber
---
src/bin/lttng-sessiond/kern-modules.h |1 -
src/bin/lttng-sessiond/modprobe.c |
Create a dynamic probe list if the LTTNG_PROBE_LIST environment variable
is set and use it to load these probes. If the environment variable is
not set all probes are loaded so the default behaviour is not changed.
Signed-off-by: Jan Glauber
---
src/bin/lttng-sessiond/kern-modules.h |2 +-
s
Hi,
I have a library which is instrumented and tracepoints are added. And i
have 2 binary's(or daemons) which try to include this library.(one binary
has instrumented code with tracepoints and other binary doesn't use
tracing)
I found that i need to instrument the daemon which includes the
instrum
Bump...
Amit Margalit
IBM XIV - Storage Reinvented
XIV-NAS Development Team
Tel. 03-689-7774
Fax. 03-689-7230
From: Amit Margalit/Israel/IBM@IBMIL
To: lttng-dev
Date: 04/02/2014 01:57 PM
Subject:[lttng-dev] Problem running lttng enable-channel shortly
after lttng create
H
On 20 Mar (13:54:55), Gerlando Falauto wrote:
> Hi,
>
> I'm trying to bring lttng-tools up to date, but I get the following message:
>
> lttng-sessiond: ht-cleanup.c:92: thread_ht_cleanup: Assertion `pollfd ==
> ht_cleanup_pipe[0]' failed.
>
> I noticed this was already filed as a bug:
> http://
Hi Jan,
Thanks for catching this. Since my patches have not been committed yet,
I'm inclined to include this fix in version 2, which I'll be sending
within the next few hours.
Regards,
Wade
Jan Glauber wrote:
> Hi Wade,
> I've tried this (very useful) new tracepoints, but I get the following
>
On 30 Mar (21:57:30), Sandeep K Chaudhary wrote:
> Hi David,
>
> Add the unit tests for the changes. Please have a look at the following
> diff for the changes in unit test file.
>
> 40,44d39
> < { "0X400", 1024 },
> < { "0x40a", 1034 },
> < { "0X40b", 10
--
Date: Thu, 3 Apr 2014 16:55:38 +0530
From: Anand Neeli
To: "lttng-dev@lists.lttng.org"
> I have a library which is instrumented and tracepoints are added. And I
> have 2 binary's (or daemons) which try to include this library
Add instrumentation for the V4L2 tracepoints that first appeared in
Linux v3.14 (commit 2d01237389dc64b37745ce87e64d6808b6eed582 in Linus's
tree).
Signed-off-by: Wade Farnsworth
---
v2: Fixed compiler warning '"V4L2_TRACE_EVENT" redefined'
instrumentation/events/lttng-module/v4l2.h | 157 +
I’d like to announce sysdig, a new open source project that I believe
could be interesting to the LTTng community. Sysdig is designed to offer
a novel, Wireshark-like approach to system tracing.
http://www.sysdig.org/
https://github.com/draios/sysdig
Sysdig is similar to lttng from the instrum
Hi Loris,
I have to say that I'm quite impress with the analysis tool you guys
have (Chisel).
Quick very useful command for monitoring use cases, very nice stuff.
Question time! Have you at some point consider using LTTng toolchain for
the tracing part? Using the lttng-modules for your probes, l
Thank you David.
We did consider the lttng toolchain, but we ended up building our own
driver for a couple of reasons:
- we do some custom work encoding events in the kernel so that they're
ready to be consumed at user level
- we perform some additional work in the kernel (e.g. resolving netw
Hi Daniel,
Thanks for your reply.
sorry for my ignorance but how are you generating libtp.so in your example?
1) Also will this solution scale if my binary depends on lots of libraries
which are instrumented?
2) i'm fine with linking statically, can we avoid LD_PRELOAD?
3) Is there any page whic
18 matches
Mail list logo
