From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subject: Some questions about Lttng Date: Mon, 18 Jun 2012 23:50:04 -0400 Message-ID: <6539770C71C3814BB0BFC2DBEBD105087948C2__32350.9197020487$1340077860$gmane$org@CORPUSMX30B.corp.emc.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1409930861==" Return-path: Received: from hop-nat-141.emc.com ([168.159.213.141] helo=mexforward.lss.emc.com) by ltt.polymtl.ca with esmtp (Exim 4.72) (envelope-from ) id 1SgpSW-0005Jp-Ad for lttng-dev@lists.lttng.org; Mon, 18 Jun 2012 23:50:28 -0400 Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5J3oMYC022740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 18 Jun 2012 23:50:22 -0400 Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for ; Mon, 18 Jun 2012 23:50:09 -0400 Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.169.196]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5J3o7h8032613 for ; Mon, 18 Jun 2012 23:50:08 -0400 Content-class: urn:content-classes:message List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: lttng-dev-bounces@lists.lttng.org To: lttng-dev@lists.lttng.org List-Id: lttng-dev@lists.lttng.org This is a multi-part message in MIME format. --===============1409930861== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD4DCE.9DD35F95" This is a multi-part message in MIME format. ------_=_NextPart_001_01CD4DCE.9DD35F95 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi folks, =20 I'm studying how to use Lttng now. I built a kernel which version is 2.6.38 and ran with lttng 2.0. I got some confused when I started to use it. Here are my questions: =20 1. I didn't see kernel patches for kernel 3.x. Does it mean kernel 3.x support it already?=20 2. I tried to do something like, dump the arguments of system call, or dump a backtrace in a specified function. But the output of lttng is very limited. Is there a way to do that with lttng? 3. I looked into some UST examples and found here are three header files: tracepoint.h, tracepoint-event.h and ust-tracepoint-event.h. They have some duplicated macro definitions like TRACEPOINT_EVENT. And the examples includes all of these three header files despite no conflict here. Could someone help to explain the intention? 4. Once I defined a tracepoint in my code, seems some initializations would register default probe into the hook point. How to disable the default probe and register my self-defined probes? 5. Does lttng-ust support dynamic traceing like kprobe? =20 I'm a newbie of lttng. Any help will be appreciated. =20 Thanks Zheng =20 =20 ------_=_NextPart_001_01CD4DCE.9DD35F95 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi = folks,

I’m studying how to use Lttng now. I built a = kernel which version is 2.6.38 and ran with lttng 2.0.

I got some confused when I started to use it. Here are = my questions:

1. I didn’t see kernel patches for kernel 3.x. = Does it mean kernel 3.x support it already?

2. I tried to do something like, dump the arguments of = system call, or dump a backtrace in a specified function. But the output = of lttng is very limited. Is there a way to do that with = lttng?

3. I looked into some UST = examples and found here are three header files: tracepoint.h, = tracepoint-event.h and ust-tracepoint-event.h. They have some duplicated = macro definitions like TRACEPOINT_EVENT.

And the examples includes all of these three header = files despite no conflict here. Could someone help to explain the = intention?

4. Once I defined a = tracepoint in my code, seems some initializations would register default = probe into the hook point. How to disable the default probe = and register my self-defined probes?

5. Does lttng-ust support dynamic traceing like = kprobe?

I’m a newbie of lttng. Any help will be = appreciated.

Thanks

Zheng

------_=_NextPart_001_01CD4DCE.9DD35F95-- --===============1409930861== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev --===============1409930861==--