Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: casmyu@gmail.com (Shouwei Li)
Subject: [ltt-dev] ltt-dev Digest, Vol 12, Issue 4
Date: Sun, 5 Apr 2009 01:43:42 +0800	[thread overview]
Message-ID: <b4aaf1450904041043l304bb601o328e7fd82119e00a@mail.gmail.com> (raw)
In-Reply-To: <20090404152752.GA2451@Krystal>

HI, All:
Thank you very much for your quick reply!
I have put the config file in the attachment. Please help me to check it.
If the modules have been build in to kernel correctly, why I can not
find the by this command:
# lsmod | grep modulesName
Now I am not sure whether I have compiled the kernel correctly, of
course I don't knwo What should I do next?
Thanks a million!

On 4/4/09, Mathieu Desnoyers <compudj at krystal.dyndns.org> wrote:
> * Shouwei Li (casmyu at gmail.com) wrote:
>> Hi, All:
>> I have installed the lttng and lttv successfully. According this manual:
>> http://ltt.polymtl.ca/svn/trunk/lttv/LTTngManual.html
>> But after this step, I did not know how to do next:
>>
>> You need to load the LTT modules to be able to control tracing from user
>> space. This is done by issuing the following commands. Note however these
>> commands load all LTT modules. Depending on what options you chose to
>> compile statically, you may not need to issue all these commands.
>>
>> modprobe ltt-trace-control
>> modprobe ltt-marker-control
>> modprobe ltt-tracer
>> modprobe ltt-serialize
>> modprobe ltt-relay
>> modprobe ipc-trace
>> ......
>>
>> I can not find these modules, even I had search them all the disk.
>>
>> Please tell me where these modules put or how to compile these modules. I
>> can
>> make sure that when I compile the lttng-kernel, I have select ALL of the
>> items
>> of LTT category.
>>
>> [root][~]# find / -name ltt-marker-control
>> [root][~]# find / -name ipc-trace
>> [root][~]# modprobe ipc-trace
>> FATAL: Module ipc_trace not found.
>> [root][~]# modprobe ltt-marker-control
>> FATAL: Module ltt_marker_control not found.
>>
>> Thanks all !
>>
>
> They are probably selected as "builtin" into your kernel image.
> Therefore you would not need to load them as modules, since they are
> already present.
>
> We could confirm this if you give us your .config or
> /boot/config-kernelversion-with-lttng.
>
> Mathieu
>
>
>> On Sat, Apr 4, 2009 at 12:00 AM,
>> <ltt-dev-request at lists.casi.polymtl.ca>wrote:
>>
>> > Send ltt-dev mailing list submissions to
>> >        ltt-dev at lists.casi.polymtl.ca
>> >
>> > To subscribe or unsubscribe via the World Wide Web, visit
>> >        http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>> > or, via email, send a message with subject or body 'help' to
>> >        ltt-dev-request at lists.casi.polymtl.ca
>> >
>> > You can reach the person managing the list at
>> >        ltt-dev-owner at lists.casi.polymtl.ca
>> >
>> > When replying, please edit your Subject line so it is more specific
>> > than "Re: Contents of ltt-dev digest..."
>> >
>> >
>> > Today's Topics:
>> >
>> >   1. Re: Where I can get some more document recently (Michel Dagenais)
>> >
>> >
>> > ----------------------------------------------------------------------
>> >
>> > Message: 1
>> > Date: Fri, 03 Apr 2009 11:13:39 -0400
>> > From: Michel Dagenais <michel.dagenais@polymtl.ca>
>> > Subject: Re: [ltt-dev] Where I can get some more document recently
>> > To: Shouwei Li <casmyu at gmail.com>
>> > Cc: ltt-dev at lists.casi.polymtl.ca
>> > Message-ID: <1238771619.15836.2.camel at localhost>
>> > Content-Type: text/plain
>> >
>> >
>> > > *** exact error that occured. This usually means GLIB is incorrectly
>> > > installed.
>> > > configure: error: glib is required in order to compile
>> > > LinuxTraceToolkit - download it from ftp://ftp.gtk.org/pub/gtk
>> > > But I have installed the libc, as follows:
>> >
>> > The GLIB and the GNU Libc are not the same thing. You need something
>> > like libglib2.0-dev Development files for the GLib library.
>> >
>> > > [root][~]# dpkg -l | grep libc6
>> > > ii  libc6                             2.9-6                    GNU C
>> >
>> >
>> >
>> >
>> > ------------------------------
>> >
>> > _______________________________________________
>> > ltt-dev mailing list
>> > ltt-dev at lists.casi.polymtl.ca
>> > http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>> >
>> >
>> > End of ltt-dev Digest, Vol 12, Issue 4
>> > **************************************
>> >
>>
>>
>>
>> --
>> Best Regards!
>> Shouwei Li
>
>> _______________________________________________
>> ltt-dev mailing list
>> ltt-dev at lists.casi.polymtl.ca
>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
>
> --
> Mathieu Desnoyers
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
>


-- 
Best Regards!
Shouwei Li
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config-2.6.29.1
Type: application/octet-stream
Size: 92951 bytes
Desc: not available
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090405/050891d3/attachment-0003.obj>


  reply	other threads:[~2009-04-04 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1238774403.2693.ltt-dev@lists.casi.polymtl.ca>
2009-04-04 11:00 ` Shouwei Li
2009-04-04 15:27   ` Mathieu Desnoyers
2009-04-04 17:43     ` Shouwei Li [this message]
2009-04-04 18:13       ` Mathieu Desnoyers
2009-04-05  2:24         ` Shouwei Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b4aaf1450904041043l304bb601o328e7fd82119e00a@mail.gmail.com \
    --to=casmyu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox