lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
* Re: 回复:Re:  回复:Re:  回复:Re: Pros and Cons of LTTng
       [not found] <tencent_7650B3E62F4AC4C75D42A69A@qq.com>
@ 2019-08-20 16:02 ` Jonathan Rajotte-Julien
       [not found] ` <20190820160220.GA31760@joraj-alpa>
  1 sibling, 0 replies; 9+ messages in thread
From: Jonathan Rajotte-Julien @ 2019-08-20 16:02 UTC (permalink / raw)
  To: 杨海; +Cc: lttng-dev

Hi Hai,

Sorry for the delay.

The main obstruction to kernel tracing support for RHEL6 is indeed the kernel.

Note that we dropped the patches in the master branch:

  commit ca2fca6b64297227b2565773a495803aa90c148e
  Author: Michael Jeanson <mjeanson@efficios.com>
  Date:   Thu Nov 8 15:24:01 2018 -0500

      Drop compat patches for kernels < 2.6.36

      Signed-off-by: Michael Jeanson <mjeanson@efficios.com>
      Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

Still, the stable 2.10 branch still carries the patches that you would need [1].
As previously mentioned, those patches might not apply cleanly since it has
been a while any effort was put in testing against RHEL6.

[1] https://github.com/lttng/lttng-modules/tree/stable-2.10/linux-patches

Cheers

On Fri, Aug 09, 2019 at 07:44:57AM +0800, 杨海 wrote:
> Hi Mathieu,
> 
> We aim to trace SYSCALL in kernel space. In general, what would be the obstacles to support RHEL6? Or what are key kernel patches to be necessary? 
> 
> 
> Regards
> Hai 
> 
> 
> 
> 
> 
> 
> 
> --------------原始邮件--------------
> 发件人:"Mathieu Desnoyers "<mathieu.desnoyers@efficios.com>;
> 发送时间:2019年7月30日(星期二) 晚上10:04
> 收件人:"杨海" <hai.yang@magic-shield.com>;
> 抄送:"Jonathan Rajotte "<jonathan.rajotte-julien@efficios.com>;"lttng-dev "<lttng-dev@lists.lttng.org>;
> 主题:Re: [lttng-dev] 回复:Re:  回复:Re:  Pros and Cons of LTTng
> -----------------------------------
> 
>  Hi,
> 
> 
> 
> The current LTTng kernel tracer (lttng-modules) supports Linux 3.0+ only.
> 
> 
> 
> If you only need to trace user-space, you might be able to use lttng-tools and lttng-ust
> 
> on an older kernel. Please refer to the README.md files of each project for information
> 
> about their environment prerequisites.
> 
> 
> 
> The RHEL6 kernel variant based on 2.6.32-2.6.35 Linux kernels has never been supported by
> 
> the LTTng 2.x kernel tracers without kernel patching.
> 
> 
> 
> Thanks,
> 
> 
> 
> Mathieu
> 
> 
> 
> ----- On Jul 29, 2019, at 8:34 PM, 杨海 <hai.yang@magic-shield.com> wrote:
> 
> Hi Mathieu,
> Thanks. I am looking for packages for older distributions like CentOS 6 (with kernel 2.6) but could not find it. And which kernel version is minimum requirement for LTTng?
> 
> Regards
> Hai
> 
> 
> 
> 
> 
> ------------------ Original ------------------
> From:  "Mathieu Desnoyers"<mathieu.desnoyers@efficios.com>;
> Date:  Thu, Jul 25, 2019 11:48 PM
> To:  "杨海"<hai.yang@magic-shield.com>; 
> Cc:  "Jonathan Rajotte"<jonathan.rajotte-julien@efficios.com>; "lttng-dev"<lttng-dev@lists.lttng.org>; 
> Subject:  Re: [lttng-dev] 回复:Re:  回复:Re:  Pros and Cons of LTTng
> 
>  
> ----- On Jul 25, 2019, at 4:21 PM, 杨海 <hai.yang@magic-shield.com> wrote:
> 
> Hi
> 
> Thanks for quick response. 
> LTTng is really impressive on performance,especially under heavy workload. When using it on critical machines,stability is also essential. 
> I wonder how LTTng is commercialized and any products or OS distributions already enabled it. 
> I took a look at lttng-modules bug list,there are a few kernel oops years ago and got resolved. May I say it is very stable or it has not been fully tested? 
> 
> Hi,
> 
> 
> EfficiOS has had commercial customers using LTTng in production for many years now.
> LTTng per-se is distributed as packages in all major Linux distributions. EfficiOS also provides
> 
> more up-to-date packages for some distributions through http://packages.efficios.com/
> 
> 
> The way we commercialize LTTng is through funding for design and implementation of
> customer's feature requests. We also provide commercial support tailored to specific
> customer's environments, which includes SLA and continuous integration testing of specific
> environments.
> 
> 
> If those are services you are interested in, please feel free to contact us in private so we
> can further discuss your needs.
> 
> 
> Best regards,
> 
> 
> Mathieu
> 
> 
> regards
> Hai
> 
> 
> 
> 
> 
> 
> --------------原始邮件--------------
> 发件人:"Jonathan Rajotte-Julien "<jonathan.rajotte-julien@efficios.com>;
> 发送时间:2019年7月23日(星期二) 上午6:20
> 收件人:"杨海" <hai.yang@magic-shield.com>;
> 抄送:"lttng-dev "<lttng-dev@lists.lttng.org>;
> 主题:Re:  回复:Re: [lttng-dev] Pros and Cons of LTTng
> -----------------------------------
> 
>  Hi,
> 
> > As to LD_PRELOAD, it is also used for privilege escalation. Will it be regarded as vulnerability and forbidden on some Linux systems?
> 
> It could yes.
> In that case you will be limited to the syscalls interface for the libc
> observability unless you instrument it and distribute it.
> 
> Cheers.
> 
> 
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> 
> 
> -- 
> 
> Mathieu Desnoyers
> EfficiOS Inc.
> http://www.efficios.com
> 
>  
> 
> 
> 
> 
> 
> 
> -- 
> 
> Mathieu Desnoyers
> EfficiOS Inc.
> http://www.efficios.com

-- 
Jonathan Rajotte-Julien
EfficiOS
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: 回复:Re:  回复:Re:  回复:Re:  Pros and Cons of LTTng
       [not found] ` <20190820160220.GA31760@joraj-alpa>
@ 2019-11-04  3:47   ` 杨海
       [not found]   ` <tencent_690A1E7757901F8A10D2CB64@qq.com>
  1 sibling, 0 replies; 9+ messages in thread
From: 杨海 @ 2019-11-04  3:47 UTC (permalink / raw)
  To: Jonathan Rajotte-Julien; +Cc: lttng-dev


[-- Attachment #1.1: Type: text/plain, Size: 6734 bytes --]

Hi


As you previously commented, “The current LTTng kernel tracer (lttng-modules) supports Linux 3.0+ only.” and we can find the support package list on http://packages.efficios.com/.&nbsp;
Does LTTng have roadmap for upcoming new kernel versions?


Regards
Hai

&nbsp;

------------------&nbsp;Original&nbsp;------------------
From: &nbsp;"Jonathan Rajotte-Julien"<jonathan.rajotte-julien@efficios.com&gt;;
Date: &nbsp;Wed, Aug 21, 2019 00:02 AM
To: &nbsp;"杨海"<hai.yang@magic-shield.com&gt;; 
Cc: &nbsp;"mathieu desnoyers"<mathieu.desnoyers@efficios.com&gt;; "lttng-dev"<lttng-dev@lists.lttng.org&gt;; 
Subject: &nbsp;Re: 回复:Re: [lttng-dev] 回复:Re:  回复:Re:  Pros and Cons of LTTng

&nbsp;

Hi Hai,

Sorry for the delay.

The main obstruction to kernel tracing support for RHEL6 is indeed the kernel.

Note that we dropped the patches in the master branch:

&nbsp; commit ca2fca6b64297227b2565773a495803aa90c148e
&nbsp; Author: Michael Jeanson <mjeanson@efficios.com&gt;
&nbsp; Date:&nbsp;&nbsp; Thu Nov 8 15:24:01 2018 -0500

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Drop compat patches for kernels < 2.6.36

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Signed-off-by: Michael Jeanson <mjeanson@efficios.com&gt;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com&gt;

Still, the stable 2.10 branch still carries the patches that you would need [1].
As previously mentioned, those patches might not apply cleanly since it has
been a while any effort was put in testing against RHEL6.

[1] https://github.com/lttng/lttng-modules/tree/stable-2.10/linux-patches

Cheers

On Fri, Aug 09, 2019 at 07:44:57AM +0800, 杨海 wrote:
&gt; Hi Mathieu,
&gt; 
&gt; We aim to trace SYSCALL in kernel space. In general, what would be the obstacles to support RHEL6? Or what are key kernel patches to be necessary? 
&gt; 
&gt; 
&gt; Regards
&gt; Hai 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; --------------原始邮件--------------
&gt; 发件人:"Mathieu Desnoyers "<mathieu.desnoyers@efficios.com&gt;;
&gt; 发送时间:2019年7月30日(星期二) 晚上10:04
&gt; 收件人:"杨海" <hai.yang@magic-shield.com&gt;;
&gt; 抄送:"Jonathan Rajotte "<jonathan.rajotte-julien@efficios.com&gt;;"lttng-dev "<lttng-dev@lists.lttng.org&gt;;
&gt; 主题:Re: [lttng-dev] 回复:Re:&nbsp; 回复:Re:&nbsp; Pros and Cons of LTTng
&gt; -----------------------------------
&gt; 
&gt;&nbsp; Hi,
&gt; 
&gt; 
&gt; 
&gt; The current LTTng kernel tracer (lttng-modules) supports Linux 3.0+ only.
&gt; 
&gt; 
&gt; 
&gt; If you only need to trace user-space, you might be able to use lttng-tools and lttng-ust
&gt; 
&gt; on an older kernel. Please refer to the README.md files of each project for information
&gt; 
&gt; about their environment prerequisites.
&gt; 
&gt; 
&gt; 
&gt; The RHEL6 kernel variant based on 2.6.32-2.6.35 Linux kernels has never been supported by
&gt; 
&gt; the LTTng 2.x kernel tracers without kernel patching.
&gt; 
&gt; 
&gt; 
&gt; Thanks,
&gt; 
&gt; 
&gt; 
&gt; Mathieu
&gt; 
&gt; 
&gt; 
&gt; ----- On Jul 29, 2019, at 8:34 PM, 杨海 <hai.yang@magic-shield.com&gt; wrote:
&gt; 
&gt; Hi Mathieu,
&gt; Thanks. I am looking for packages for older distributions like CentOS 6 (with kernel 2.6) but could not find it. And which kernel version is minimum requirement for LTTng?
&gt; 
&gt; Regards
&gt; Hai
&gt; 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; ------------------ Original ------------------
&gt; From:&nbsp; "Mathieu Desnoyers"<mathieu.desnoyers@efficios.com&gt;;
&gt; Date:&nbsp; Thu, Jul 25, 2019 11:48 PM
&gt; To:&nbsp; "杨海"<hai.yang@magic-shield.com&gt;; 
&gt; Cc:&nbsp; "Jonathan Rajotte"<jonathan.rajotte-julien@efficios.com&gt;; "lttng-dev"<lttng-dev@lists.lttng.org&gt;; 
&gt; Subject:&nbsp; Re: [lttng-dev] 回复:Re:&nbsp; 回复:Re:&nbsp; Pros and Cons of LTTng
&gt; 
&gt;&nbsp; 
&gt; ----- On Jul 25, 2019, at 4:21 PM, 杨海 <hai.yang@magic-shield.com&gt; wrote:
&gt; 
&gt; Hi
&gt; 
&gt; Thanks for quick response. 
&gt; LTTng is really impressive on performance,especially under heavy workload. When using it on critical machines,stability is also essential. 
&gt; I wonder how LTTng is commercialized and any products or OS distributions already enabled it. 
&gt; I took a look at lttng-modules bug list,there are a few kernel oops years ago and got resolved. May I say it is very stable or it has not been fully tested? 
&gt; 
&gt; Hi,
&gt; 
&gt; 
&gt; EfficiOS has had commercial customers using LTTng in production for many years now.
&gt; LTTng per-se is distributed as packages in all major Linux distributions. EfficiOS also provides
&gt; 
&gt; more up-to-date packages for some distributions through http://packages.efficios.com/
&gt; 
&gt; 
&gt; The way we commercialize LTTng is through funding for design and implementation of
&gt; customer's feature requests. We also provide commercial support tailored to specific
&gt; customer's environments, which includes SLA and continuous integration testing of specific
&gt; environments.
&gt; 
&gt; 
&gt; If those are services you are interested in, please feel free to contact us in private so we
&gt; can further discuss your needs.
&gt; 
&gt; 
&gt; Best regards,
&gt; 
&gt; 
&gt; Mathieu
&gt; 
&gt; 
&gt; regards
&gt; Hai
&gt; 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; --------------原始邮件--------------
&gt; 发件人:"Jonathan Rajotte-Julien "<jonathan.rajotte-julien@efficios.com&gt;;
&gt; 发送时间:2019年7月23日(星期二) 上午6:20
&gt; 收件人:"杨海" <hai.yang@magic-shield.com&gt;;
&gt; 抄送:"lttng-dev "<lttng-dev@lists.lttng.org&gt;;
&gt; 主题:Re:&nbsp; 回复:Re: [lttng-dev] Pros and Cons of LTTng
&gt; -----------------------------------
&gt; 
&gt;&nbsp; Hi,
&gt; 
&gt; &gt; As to LD_PRELOAD, it is also used for privilege escalation. Will it be regarded as vulnerability and forbidden on some Linux systems?
&gt; 
&gt; It could yes.
&gt; In that case you will be limited to the syscalls interface for the libc
&gt; observability unless you instrument it and distribute it.
&gt; 
&gt; Cheers.
&gt; 
&gt; 
&gt; 
&gt; _______________________________________________
&gt; lttng-dev mailing list
&gt; lttng-dev@lists.lttng.org
&gt; https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
&gt; 
&gt; 
&gt; -- 
&gt; 
&gt; Mathieu Desnoyers
&gt; EfficiOS Inc.
&gt; http://www.efficios.com
&gt; 
&gt;&nbsp; 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; 
&gt; -- 
&gt; 
&gt; Mathieu Desnoyers
&gt; EfficiOS Inc.
&gt; http://www.efficios.com

-- 
Jonathan Rajotte-Julien
EfficiOS

[-- Attachment #1.2: Type: text/html, Size: 8883 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: 回复:Re:  回复:Re:  回复:Re: Pros and Cons of LTTng
       [not found]   ` <tencent_690A1E7757901F8A10D2CB64@qq.com>
@ 2019-11-04 16:55     ` Jonathan Rajotte-Julien
       [not found]     ` <20191104165454.GA2344@joraj-alpa>
  1 sibling, 0 replies; 9+ messages in thread
From: Jonathan Rajotte-Julien @ 2019-11-04 16:55 UTC (permalink / raw)
  To: 杨海; +Cc: lttng-dev

Hi,

On Mon, Nov 04, 2019 at 11:47:58AM +0800, 杨海 wrote:
> Hi
> 
> 
> As you previously commented, “The current LTTng kernel tracer (lttng-modules) supports Linux 3.0+ only.” and we can find the support package list on http://packages.efficios.com/.&nbsp;
> Does LTTng have roadmap for upcoming new kernel versions?

I presume you are explicitly asking for RHEL & SUSE kernels. The current
packages for these distro are maintained on a best effort and commercial
incentive of EfficiOS. If you are interested in supporting this effort please
contact sales@efficios.com.

As for the actual upstream kernel, we are monitoring [1] all new kernels and
stable branches.


[1] https://ci.lttng.org/view/LTTng-modules/
    https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_stable-2.9_build-vanilla/
    https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_stable-2.10_build-vanilla/
    https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_stable-2.11_build-vanilla/
    https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_master_build-vanilla/

Cheers
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: 回复:Re:  回复:Re:  回复:Re:  Pros and Cons of LTTng
       [not found]     ` <20191104165454.GA2344@joraj-alpa>
@ 2019-11-06  3:59       ` 杨海
       [not found]       ` <tencent_728E005C598C6B7038AD5A41@qq.com>
  1 sibling, 0 replies; 9+ messages in thread
From: 杨海 @ 2019-11-06  3:59 UTC (permalink / raw)
  To: Jonathan Rajotte-Julien; +Cc: lttng-dev


[-- Attachment #1.1: Type: text/plain, Size: 2118 bytes --]

Thanks Jonathan. Regarding to the CI MTTR/MTTF test results, it varies from time to time, and on master/stable branches.&nbsp;
1. it monitors new Linux kernels, so the CI job may use newer kernel version than months ago?
2. What would be the criteria of MTBF here?


MTTRLast 7 Days0 ms
Last 30 Days12 hr
All Time3 days 21 hr
MTTFLast 7 Days0 ms
Last 30 Days12 days
All Time29 days
Standard DeviationLast 7 Days21 min
Last 30 Days30 min
All Time44 min


Regards
Hai
&nbsp;
------------------&nbsp;Original&nbsp;------------------
From: &nbsp;"Jonathan Rajotte-Julien"<jonathan.rajotte-julien@efficios.com&gt;;
Date: &nbsp;Tue, Nov 5, 2019 00:55 AM
To: &nbsp;"杨海"<hai.yang@magic-shield.com&gt;; 
Cc: &nbsp;"mathieu desnoyers"<mathieu.desnoyers@efficios.com&gt;; "lttng-dev"<lttng-dev@lists.lttng.org&gt;; 
Subject: &nbsp;Re: 回复:Re: [lttng-dev] 回复:Re:  回复:Re:  Pros and Cons of LTTng

&nbsp;

Hi,

On Mon, Nov 04, 2019 at 11:47:58AM +0800, 杨海 wrote:
&gt; Hi
&gt; 
&gt; 
&gt; As you previously commented, “The current LTTng kernel tracer (lttng-modules) supports Linux 3.0+ only.” and we can find the support package list on http://packages.efficios.com/.&amp;nbsp;
&gt; Does LTTng have roadmap for upcoming new kernel versions?

I presume you are explicitly asking for RHEL &amp; SUSE kernels. The current
packages for these distro are maintained on a best effort and commercial
incentive of EfficiOS. If you are interested in supporting this effort please
contact sales@efficios.com.

As for the actual upstream kernel, we are monitoring [1] all new kernels and
stable branches.


[1] https://ci.lttng.org/view/LTTng-modules/
&nbsp;&nbsp;&nbsp; https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_stable-2.9_build-vanilla/
&nbsp;&nbsp;&nbsp; https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_stable-2.10_build-vanilla/
&nbsp;&nbsp;&nbsp; https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_stable-2.11_build-vanilla/
&nbsp;&nbsp;&nbsp; https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_master_build-vanilla/

Cheers

[-- Attachment #1.2: Type: text/html, Size: 19030 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: 回复:Re:  回复:Re:  回复:Re: Pros and Cons of LTTng
       [not found]       ` <tencent_728E005C598C6B7038AD5A41@qq.com>
@ 2019-11-06 17:18         ` Jonathan Rajotte-Julien
       [not found]         ` <20191106171800.GA26063@joraj-alpa>
  1 sibling, 0 replies; 9+ messages in thread
From: Jonathan Rajotte-Julien @ 2019-11-06 17:18 UTC (permalink / raw)
  To: 杨海; +Cc: lttng-dev

Hi,

On Wed, Nov 06, 2019 at 11:59:41AM +0800, 杨海 wrote:
> Thanks Jonathan. Regarding to the CI MTTR/MTTF test results, it varies from time to time, and on master/stable branches.&nbsp;
> 1. it monitors new Linux kernels, so the CI job may use newer kernel version than months ago?

Not sure of the question here but here more information on how to jobs works.

The job monitor all kernel tags that we deems pertinent for example for the
vanilla kernel (linux-stable) with the lttng-modules master branch [1]:

  09:13:52 Building the following kernel versions:
  09:13:52 v3.0.101
  09:13:52 v3.1.10
  09:13:52 v3.2.102
  09:13:52 v3.3.8
  09:13:52 v3.4.113
  09:13:52 v3.5.7
  09:13:52 v3.6.11
  09:13:52 v3.7.10
  09:13:52 v3.8.13
  09:13:52 v3.9.11
  09:13:52 v3.10.108
  09:13:52 v3.11.10
  09:13:52 v3.12.74
  09:13:52 v3.13.11
  09:13:52 v3.14.79
  09:13:52 v3.15.10
  09:13:52 v3.16.76
  09:13:52 v3.17.8
  09:13:52 v3.18.140
  09:13:52 v3.19.8
  09:13:52 v4.0.9
  09:13:52 v4.1.52
  09:13:52 v4.2.8
  09:13:52 v4.3.6
  09:13:52 v4.4.199
  09:13:52 v4.5.7
  09:13:52 v4.6.7
  09:13:52 v4.7.10
  09:13:52 v4.8.17
  09:13:52 v4.9.199
  09:13:52 v4.10.17
  09:13:52 v4.11.12
  09:13:52 v4.12.14
  09:13:52 v4.13.16
  09:13:52 v4.14.152
  09:13:52 v4.15.18
  09:13:52 v4.16.18
  09:13:52 v4.17.19
  09:13:52 v4.18.20
  09:13:52 v4.19.82
  09:13:52 v4.20.17
  09:13:52 v5.0.21
  09:13:52 v5.1.21
  09:13:52 v5.2.21
  09:13:52 v5.3.9
  09:13:52 v5.4-rc6

We always track the latest tag of each branch. This does not mean that we do not
support smaller tag of a branch, only that support is a best effort based on
user feedback. Tracking all tags would represent a monumental effort and would
require way more resource overall. Not something we are against, simply that we
do not have the resource for it.

[1] https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_master_build-vanilla/

Note the last rc kernel tag.

Note that we also perform this for some distros and their kernels:

https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_master_crossbuild-xenial/
https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_master_crossbuild-bionic/

I guess that it is true that we do not test against past kernel tag for each
branch. Given our history and process, most time that lttng-modules is broken is
that distro are taking liberty on patch backporting. These get fixed asap and
backported to all supported lttng-modules stable branches. 
> 2. What would be the criteria of MTBF here?

Note that these statistics have little to no value here due to the presence of the
testing against RC tags. These tags will breaks lttng-modules one way or another
and it is a good thing. This allows us to keep up to date with upstream.
The only pertinent value is the MTTR here. It shows our responsiveness to
external change.

A better representation of our MTTR would be the jobs following distros:

https://ci.lttng.org/view/LTTng-modules/job/lttng-modules_master_build-xenial/

MTTR    Last 7 Days    0 ms
        Last 30 Days   0 ms
        All Time       15 hr
MTTF    Last 7 Days    0 ms
        Last 30 Days   0 ms
        All Time       4 mo 5 days

Here our MTTR is 15h. Which is quite quick considering the context of tracking
kernel outside of our control.

MTTR is from the moment the CI detect a problem and that we provide a fix for
it.

MTTF is not something we can have control over since the source is completely
external. Except for the rare event that the infrastructure is deficient.

TBH these statistic have little to no meaning in this context.

Cheers

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 9+ messages in thread

* documentation about CTF event payload
       [not found]         ` <20191106171800.GA26063@joraj-alpa>
@ 2019-11-18  1:54           ` 杨海
       [not found]           ` <tencent_2D749AE44D158E681A6166AC@qq.com>
  1 sibling, 0 replies; 9+ messages in thread
From: 杨海 @ 2019-11-18  1:54 UTC (permalink / raw)
  To: lttng-dev


[-- Attachment #1.1: Type: text/plain, Size: 262 bytes --]

Hi


As LTTng generated CTF and babeltrace parse it, we have the output as attached. We saw events such as sched_switch, but the payload cannot be understood easily. Where we can find the document to explain the LTTng payload and parameters?


Regards
Hai

[-- Attachment #1.2: Type: text/html, Size: 538 bytes --]

[-- Attachment #2: 2D6490484440066845DC52CC7D63804A.jpg --]
[-- Type: application/octet-stream, Size: 86138 bytes --]

[-- Attachment #3: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: documentation about CTF event payload
       [not found]           ` <tencent_2D749AE44D158E681A6166AC@qq.com>
@ 2019-11-20  2:25             ` 杨海
       [not found]             ` <tencent_3EE1250109255673062B819B@qq.com>
  1 sibling, 0 replies; 9+ messages in thread
From: 杨海 @ 2019-11-20  2:25 UTC (permalink / raw)
  To: lttng-dev


[-- Attachment #1.1: Type: text/plain, Size: 754 bytes --]

To be more specific, I suppose we can refer to instrumentation\syscalls\3.10.0-rc7\x86-64-syscalls-3.10.0-rc7 for the payload format of syscall event. Is it exactly in the CTF syscall event?


Regards
Hai
&nbsp;
------------------&nbsp;Original&nbsp;------------------
From: &nbsp;"杨海"<hai.yang@magic-shield.com&gt;;
Date: &nbsp;Mon, Nov 18, 2019 09:54 AM
To: &nbsp;"lttng-dev"<lttng-dev@lists.lttng.org&gt;; 

Subject: &nbsp;documentation about CTF event payload

&nbsp;

Hi


As LTTng generated CTF and babeltrace parse it, we have the output as attached. We saw events such as sched_switch, but the payload cannot be understood easily. Where we can find the document to explain the LTTng payload and parameters?


Regards
Hai

[-- Attachment #1.2: Type: text/html, Size: 1304 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: documentation about CTF event payload
       [not found]             ` <tencent_3EE1250109255673062B819B@qq.com>
@ 2019-11-20 14:32               ` Mathieu Desnoyers
       [not found]               ` <1361419525.123.1574260355956.JavaMail.zimbra@efficios.com>
  1 sibling, 0 replies; 9+ messages in thread
From: Mathieu Desnoyers @ 2019-11-20 14:32 UTC (permalink / raw)
  To: 杨海; +Cc: lttng-dev


[-- Attachment #1.1: Type: text/plain, Size: 1500 bytes --]

For the system call payload documentation, you might want to refer to the Linux system call 
man pages. 

For internal kernel tracepoints like sched_switch, there is no documentation of the meaning of 
each field at the moment. This state is the same as the upstream Linux kernel trace event. You'll 
have to figure it out on your own. Documenting each field of the ~500-1000 Linux kernel tracepoints 
is no small task. 

Thanks, 

Mathieu 

----- On Nov 19, 2019, at 9:25 PM, 杨海 <hai.yang@magic-shield.com> wrote: 

> To be more specific, I suppose we can refer to
> instrumentation\syscalls\3.10.0-rc7\x86-64-syscalls-3.10.0-rc7 for the payload
> format of syscall event. Is it exactly in the CTF syscall event?

> Regards
> Hai
> ------------------ Original ------------------
> From: "杨海"<hai.yang@magic-shield.com>;
> Date: Mon, Nov 18, 2019 09:54 AM
> To: "lttng-dev"<lttng-dev@lists.lttng.org>;
> Subject: documentation about CTF event payload
> Hi

> As LTTng generated CTF and babeltrace parse it, we have the output as attached.
> We saw events such as sched_switch, but the payload cannot be understood
> easily. Where we can find the document to explain the LTTng payload and
> parameters?

> Regards
> Hai

> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers 
EfficiOS Inc. 
http://www.efficios.com 

[-- Attachment #1.2: Type: text/html, Size: 2702 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: documentation about CTF event payload
       [not found]               ` <1361419525.123.1574260355956.JavaMail.zimbra@efficios.com>
@ 2019-11-20 15:43                 ` Matthew Khouzam via lttng-dev
  0 siblings, 0 replies; 9+ messages in thread
From: Matthew Khouzam via lttng-dev @ 2019-11-20 15:43 UTC (permalink / raw)
  To: Mathieu Desnoyers, 杨海; +Cc: lttng-dev


[-- Attachment #1.1: Type: text/plain, Size: 3150 bytes --]

Hi, I would like to add it is an insane amount of work.

I have documented some tracepoints. Maybe this can help. https://git.eclipse.org/c/tracecompass/org.eclipse.tracecompass.git/tree/analysis/org.eclipse.tracecompass.analysis.os.linux.core/src/org/eclipse/tracecompass/analysis/os/linux/core/trace/IKernelAnalysisEventLayout.java<https://git.eclipse.org/c/tracecompass/org.eclipse.tracecompass.git/tree/analysis/org.eclipse.tracecompass.analysis.os.linux.core/src/org/eclipse/tracecompass/analysis/os/linux/core/trace/IKernelAnalysisEventLayout.java?id=01f2a5074ceebbc1ceaf2643c1aff5168a61ed4b>

For the syscalls, take a look at this, it may help?
https://git.eclipse.org/c/tracecompass/org.eclipse.tracecompass.git/tree/analysis/org.eclipse.tracecompass.analysis.os.linux.core/res/syscalls.tsv

Also, if you feel like enhancing the list, we'd be thrilled. 😉

As the author of these doc patches, I can confirm, it's a lot of not rewarding work.

Cheers
________________________________
From: lttng-dev <lttng-dev-bounces@lists.lttng.org> on behalf of Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Sent: Wednesday, November 20, 2019 9:32 AM
To: 杨海 <hai.yang@magic-shield.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] documentation about CTF event payload

For the system call payload documentation, you might want to refer to the Linux system call
man pages.

For internal kernel tracepoints like sched_switch, there is no documentation of the meaning of
each field at the moment. This state is the same as the upstream Linux kernel trace event. You'll
have to figure it out on your own. Documenting each field of the ~500-1000 Linux kernel tracepoints
is no small task.

Thanks,

Mathieu

----- On Nov 19, 2019, at 9:25 PM, 杨海 <hai.yang@magic-shield.com> wrote:
To be more specific, I suppose we can refer to instrumentation\syscalls\3.10.0-rc7\x86-64-syscalls-3.10.0-rc7 for the payload format of syscall event. Is it exactly in the CTF syscall event?

Regards
Hai

------------------ Original ------------------
From:  "杨海"<hai.yang@magic-shield.com>;
Date:  Mon, Nov 18, 2019 09:54 AM
To:  "lttng-dev"<lttng-dev@lists.lttng.org>;
Subject:  documentation about CTF event payload

Hi

As LTTng generated CTF and babeltrace parse it, we have the output as attached. We saw events such as sched_switch, but the payload cannot be understood easily. Where we can find the document to explain the LTTng payload and parameters?

Regards
Hai

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev<https://protect2.fireeye.com/v1/url?k=b57ee672-e9f43364-b57ea6e9-862f14a9365e-4edf64ec28cf8a82&q=1&e=f6fc5282-6aa8-47e6-b1ba-c0f4d8c08799&u=https%3A%2F%2Flists.lttng.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Flttng-dev>

--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com<https://protect2.fireeye.com/v1/url?k=0d1e3efa-5194ebec-0d1e7e61-862f14a9365e-4d330cf58530a29c&q=1&e=f6fc5282-6aa8-47e6-b1ba-c0f4d8c08799&u=http%3A%2F%2Fwww.efficios.com%2F>

[-- Attachment #1.2: Type: text/html, Size: 6440 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2019-11-20 15:43 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <tencent_7650B3E62F4AC4C75D42A69A@qq.com>
2019-08-20 16:02 ` 回复:Re: 回复:Re: 回复:Re: Pros and Cons of LTTng Jonathan Rajotte-Julien
     [not found] ` <20190820160220.GA31760@joraj-alpa>
2019-11-04  3:47   ` 杨海
     [not found]   ` <tencent_690A1E7757901F8A10D2CB64@qq.com>
2019-11-04 16:55     ` Jonathan Rajotte-Julien
     [not found]     ` <20191104165454.GA2344@joraj-alpa>
2019-11-06  3:59       ` 杨海
     [not found]       ` <tencent_728E005C598C6B7038AD5A41@qq.com>
2019-11-06 17:18         ` Jonathan Rajotte-Julien
     [not found]         ` <20191106171800.GA26063@joraj-alpa>
2019-11-18  1:54           ` documentation about CTF event payload 杨海
     [not found]           ` <tencent_2D749AE44D158E681A6166AC@qq.com>
2019-11-20  2:25             ` 杨海
     [not found]             ` <tencent_3EE1250109255673062B819B@qq.com>
2019-11-20 14:32               ` Mathieu Desnoyers
     [not found]               ` <1361419525.123.1574260355956.JavaMail.zimbra@efficios.com>
2019-11-20 15:43                 ` Matthew Khouzam via lttng-dev

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).