[ltt-dev] some problems on installing LTTng 0.115 for Linux 2.6.29

zengshan227 zengshan227 at gmail.com
Fri Apr 10 07:19:15 EDT 2009


hi Mathieu :
    I am tring to install the LTTng 0.115 for Linux 2.6.29, I do that by referring to this url: http://ltt.polymtl.ca/svn/trunk/lttv/LTTngManual.html#section1
and When I run the " make" command , I got the following message:
 
scripts/kconfig/conf -s arch/x86/Kconfig
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-x86
  CC      kernel/bounds.s
  GEN     include/linux/bounds.h
  CC      arch/x86/kernel/asm-offsets.s
In file included from include/linux/crypto.h:21,
                 from arch/x86/kernel/asm-offsets_32.c:7,
                 from arch/x86/kernel/asm-offsets.c:2:
include/linux/module.h:629: error: static declaration of '_module_imv_update'follows non-static declaration
include/linux/module.h:489: error: previous declaration of ' _module_imv_update'  was here
include/linux/module.h:633: error: redefinition of ' module_imv_update'
include/linux/immediate.h:75: error: previous definition of ' module_imv_update'  was here
make[1]: *** [arch/x86/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2

I search for the reason of this problem ,and I found may be it is the problem when " patching file include/linux/immediate.h"


The next patch would create the file include/linux/immediate.h,
which already exists!  Assume -R? [n] y
patching file include/linux/immediate.h
Hunk #1 FAILED at 1.
File include/linux/immediate.h is not empty after patch, as expected
1 out of 1 hunk FAILED -- saving rejects to file include/linux/immediate.h.rej
patching file include/linux/marker.h
Hunk #1 FAILED at 14.
Hunk #2 FAILED at 44.
Hunk #3 FAILED at 87.
3 out of 3 hunks FAILED -- saving rejects to file include/linux/marker.h.rej
patching file kernel/marker.c
Hunk #1 FAILED at 24.
Hunk #2 FAILED at 533.
Hunk #3 FAILED at 563.
Hunk #4 FAILED at 579.
Hunk #5 FAILED at 594.
Hunk #6 FAILED at 658.
6 out of 6 hunks FAILED -- saving rejects to file kernel/marker.c.rej


Can anybody help me what can I do to settle this problem?

Best regards!

2009-04-10 



zengshan227 



发件人: Mathieu Desnoyers 
发送时间: 2009-04-10  02:56:09 
收件人: 曾珊; pierre-marc.fournier at polymtl.ca 
抄送: ltt-dev at lists.casi.polymtl.ca; linux-kernel at vger.kernel.org 
主题: Re: LTTng 0.115 for Linux 2.6.29 
 
* 曾珊 (zengshan227 at gmail.com) wrote:
> can ltt been used in network IO tracing under the environment of KVM?
> 
> hi:
>   what I meant path tracing is that we want to get the ingressing path of a
> packet under the environment of KVM (Kernel based Virtual Machine ), what we
> want to know exactly is the ingressing path of a packet from the host
> machine to the virtual machine ,
> ps: KVM used Qemu to process its network I/O , which is actually a process
> in the host OS.
>   Any ideas?
>   Thank you very much~

Yes, Pierre-Marc has done some work to make sure LTTV can show traces
from both the host kernel and a virtual machine together and therefore
allow the kind of analysis you are looking for. I am putting him in CC
so he can explain how to use his work.

Mathieu

> 
> 2009/3/24 Mathieu Desnoyers  <compudj at krystal.dyndns.org >
> 
>  > Hi,
>  >
>  > I just released LTTng 0.115 for Linux 2.6.29. Happy tracing. :)
>  >
>  > It is, as always, available both as a patchset and as a git tree. See
>  > http://www.lttng.org for details.
>  >
>  > Mathieu
>  >
>  >
>  > --
>  > Mathieu Desnoyers
>  > OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
>  > --
>  > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>  > the body of a message to majordomo at vger.kernel.org
>  > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>  > Please read the FAQ at  http://www.tux.org/lkml/
>  >

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090410/19263575/attachment-0003.htm>


More information about the lttng-dev mailing list