From: klaus.dannecker@gmx.de (Klaus Dannecker)
Subject: [lttng-dev] make a trace_event in a modul (driver)
Date: Thu, 21 Nov 2013 10:48:59 +0100 [thread overview]
Message-ID: <528DD70B.8040504@gmx.de> (raw)
In-Reply-To: <5283B8BD.9020703@gmx.de>
Hi,
Nobody can help me?
now i have ubuntu 13.10 installed in a vmware.
but i have the same error!
s$ sudo make modules_install
make -C /lib/modules/3.11.0-12-generic/build
M=/home/klaus/lttng_src/lttng-modules modules_install
make[1]: Entering directory `/usr/src/linux-headers-3.11.0-12-generic'
INSTALL /home/klaus/lttng_src/lttng-modules/lib/lttng-lib-ring-buffer.ko
Can't read private key
....
lsmod | grep lttng
-> no module found
Thanks!
Am 13.11.2013 18:37, schrieb Klaus Dannecker:
>
> Am 09.11.2013 09:33, schrieb Klaus Dannecker:
>> Hi,
>> I want to write a driver with trace events.
>> In the first step i compile the example trace-events-sample.c with
>> the makefile:
>>
>> ifneq ($(KERNELRELEASE),)
>> obj-m := modul_trace-events-sample.o
>> modul_trace-events-sample-y := trace-events-sample.o
>> ccflags-y := -I$(src)
>> else
>> KDIR ?= /lib/modules/`uname -r`/build
>> default:
>> $(MAKE) -C $(KDIR) M=$$PWD
>> endif
>>
>> now i get the modul_trace-events-sample.ko File.
>> now:
>> insmod modul_trace-events-sample.ko
>> lttng create
>> lttng enable-event -k -a
>> lttng start
>> ...wait...
>> lttng stop
>> lttng destroy
>>
>> now i look the result in the eclise viewer, but i found event
>> "trace_foo_bar" not in the session!
>> what am I doing wrong?
>>
>> I use ubuntu 13.04 in a vmware
>>
>> Thanks
>>
>> _______________________________________________
> Hi,
>
> now i found a answer:
> http://lists.lttng.org/pipermail/lttng-dev/2013-October/021540.html
> now i download the lttng-module and compiled it.
> |$ git clone git://git.lttng.org/lttng-modules.git
> ||$ cd lttng-tools|
> |$ make|
> |$ sudo make modules_install
> |here I get error
> INSTALL /mnt/hgfs/shared_Folder/lttng-modules/lib/lttng-lib-ring-buffer.ko
> Can't read private key
> ...
> what does that mean?
> what should I do?
>
> please help me!
>
> another question:
> when i create atrace events in module_a,
> can i use it in module_b?
> if yes,what should I do?
> thanks Klaus
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20131121/68863dbb/attachment-0001.html>
next prev parent reply other threads:[~2013-11-21 9:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 8:33 Klaus Dannecker
2013-11-13 17:37 ` Klaus Dannecker
2013-11-21 9:48 ` Klaus Dannecker [this message]
2013-11-21 15:49 ` Jérémie Galarneau
2013-11-21 16:42 ` Klaus Dannecker
2013-11-21 17:41 ` Jérémie Galarneau
2013-11-22 10:54 ` Klaus Dannecker
2013-11-22 16:12 ` Jérémie Galarneau
2013-11-22 17:33 ` Klaus Dannecker
2013-11-22 18:41 ` Jérémie Galarneau
2013-11-22 19:06 ` Jérémie Galarneau
2013-11-22 19:07 ` Francis Giraldeau
2013-11-22 18:54 Thibault, Daniel
2013-11-22 19:01 ` Jérémie Galarneau
2013-11-24 11:43 ` Klaus Dannecker
2013-11-24 16:01 ` Jérémie Galarneau
2013-11-24 18:26 ` Klaus Dannecker
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=528DD70B.8040504@gmx.de \
--to=klaus.dannecker@gmx.de \
/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