[ltt-dev] LTTng 0.115 for Linux 2.6.29

[ltt-dev] LTTng 0.115 for Linux 2.6.29

[Mathieu Desnoyers]

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

[ltt-dev] LTTng 0.115 for Linux 2.6.29

[曾珊]

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~

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/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090409/770ab76c/attachment-0003.htm>

[ltt-dev] LTTng 0.115 for Linux 2.6.29

[Mathieu Desnoyers]

* ?? (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

[ltt-dev] LTTng 0.115 for Linux 2.6.29

[zengshan227]

It is really very kind of you to reply to me!
Thanks a bunch~


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/52fd4773/attachment-0003.htm>

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

[zengshan227]

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>

[ltt-dev] Using LTTng to trace a host and its virtual machines

[Pierre-Marc Fournier]

Hello Zengshan,

There are two things here.

1. Tracing a host and a virtual machine simultaneously
2. Following a packet through those machines

Tracing a host and a virtual machine is not too difficult. It's normally
just a matter of recording a trace on the host and recording traces in
the virtual machines, all at the same time. Then you open them both in
LTTV and see them merged. But at least two things can cause problems.
The first is that you need a common time source between all these
machines. On a single core x86, you can use the TSC, which is supposed
to be available in the virtual machines too. But you must make sure the
virtualization system does not change the TSC before it presents it to
the virtual machine. For example, it could save it when the virtual
machine is scheduled out and restore it to that value when it's
scheduled back in, in other words "virtualizing" the TSC. I think kvm
does this or some other form of mangling by default. You need to do
whatever needs to be done on your specific architecture to get a common
time source. The other thing that can cause problems is that your
virtual cpus might think they are not running exactly at the same speed
as host cpus. Frequencies are determined when the system boots. The
frequency is written in the trace and is used to convert TSCs in
seconds. If the host and VMs have the same time source but think they
are running at slightly different frequencies, the merge will not work
properly in LTTV. I commited a patch in lttv a while ago so that the
frequency of the first trace is used for all the other traces that are
loaded. So this shouldn't be a problem anymore.

The other part of your question concerns following of packets through
the virtualization border. For that, you will likely need to add
supplementary instrumentation. Perhaps you will need to instrument kvm
itself. One way to do it would be assigning identifiers to packets and
to refer to those identifiers in events.

I hope this helps a bit.

pmf

zengshan227 wrote:
>  
> hi Pierre-Marc :
>    Mathieu Desnoyers (CC-ed in this mail) who is so kind to tell me that
> you have  done some work to make sure LTTV can show traces
> from both the host kernel and a virtual machine together, since I am now
> pursing tracing network I/O path under the environment of KVM,  what I
> want to know exactly is the ingressing path of a packet from the host
> machine to the virtual machine , Can your work allow the kind of analysis?
>  
> Thank you very much ~
> Best Regards!
>  
> 2009-04-10
> ------------------------------------------------------------------------
> zengshan227
> ------------------------------------------------------------------------
> *????* zengshan227
> *?????* 2009-04-10 10:34:08
> *????* pierre-marc.fournier at polymtl.ca
> *???* Mathieu Desnoyers
> *???* Re: Re: LTTng 0.115 for Linux 2.6.29
>  
> hi Pierre-Marc :
>    I know from Mathieu Desnoyers (CC-ed in this mail) that you
> have  done some work to make sure LTTV can show traces
> from both the host kernel and a virtual machine together, since I am now
> pursing tracing network I/O path under the environment of KVM,  what I
> want to know exactly is the ingressing path of a packet from the host
> machine to the virtual machine , Can your work allow the kind of analysis?
>  
> Thank you very much ~
> 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 <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

[ltt-dev] Using LTTng to trace a host and its virtual machines

[zengshan227]

Thank you very much for your replying , It really helps.
I will try to practice what you said, and may interrupt you if I have some problems~

Best regards~


2009-04-17 



zengshan227 



???? Pierre-Marc Fournier 
????? 2009-04-17  00:32:35 
???? zengshan227 
??? Mathieu Desnoyers; ltt-dev at lists.casi.polymtl.ca 
??? Using LTTng to trace a host and its virtual machines 
 
Hello Zengshan,

There are two things here.

1. Tracing a host and a virtual machine simultaneously
2. Following a packet through those machines

Tracing a host and a virtual machine is not too difficult. It's normally
just a matter of recording a trace on the host and recording traces in
the virtual machines, all at the same time. Then you open them both in
LTTV and see them merged. But at least two things can cause problems.
The first is that you need a common time source between all these
machines. On a single core x86, you can use the TSC, which is supposed
to be available in the virtual machines too. But you must make sure the
virtualization system does not change the TSC before it presents it to
the virtual machine. For example, it could save it when the virtual
machine is scheduled out and restore it to that value when it's
scheduled back in, in other words "virtualizing" the TSC. I think kvm
does this or some other form of mangling by default. You need to do
whatever needs to be done on your specific architecture to get a common
time source. The other thing that can cause problems is that your
virtual cpus might think they are not running exactly at the same speed
as host cpus. Frequencies are determined when the system boots. The
frequency is written in the trace and is used to convert TSCs in
seconds. If the host and VMs have the same time source but think they
are running at slightly different frequencies, the merge will not work
properly in LTTV. I commited a patch in lttv a while ago so that the
frequency of the first trace is used for all the other traces that are
loaded. So this shouldn't be a problem anymore.

The other part of your question concerns following of packets through
the virtualization border. For that, you will likely need to add
supplementary instrumentation. Perhaps you will need to instrument kvm
itself. One way to do it would be assigning identifiers to packets and
to refer to those identifiers in events.

I hope this helps a bit.

pmf

zengshan227 wrote:
>  
> hi Pierre-Marc :
>    Mathieu Desnoyers (CC-ed in this mail) who is so kind to tell me that
> you have  done some work to make sure LTTV can show traces
> from both the host kernel and a virtual machine together, since I am now
> pursing tracing network I/O path under the environment of KVM,  what I
> want to know exactly is the ingressing path of a packet from the host
> machine to the virtual machine , Can your work allow the kind of analysis?
>  
> Thank you very much ~
> Best Regards!
>  
> 2009-04-10
> ------------------------------------------------------------------------
> zengshan227
> ------------------------------------------------------------------------
> *????* zengshan227
> *?????* 2009-04-10 10:34:08
> *????* pierre-marc.fournier at polymtl.ca
> *???* Mathieu Desnoyers
> *???* Re: Re: LTTng 0.115 for Linux 2.6.29
>  
> hi Pierre-Marc :
>    I know from Mathieu Desnoyers (CC-ed in this mail) that you
> have  done some work to make sure LTTV can show traces
> from both the host kernel and a virtual machine together, since I am now
> pursing tracing network I/O path under the environment of KVM,  what I
> want to know exactly is the ingressing path of a packet from the host
> machine to the virtual machine , Can your work allow the kind of analysis?
>  
> Thank you very much ~
> 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  <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/20090417/59266bc3/attachment-0003.htm>