Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: laijs@cn.fujitsu.com (Lai Jiangshan)
Subject: [ltt-dev] [PATCH v2] add tracepoints of panic and kexec
Date: Fri, 16 Jan 2009 14:47:02 +0800	[thread overview]
Message-ID: <49702D66.80609@cn.fujitsu.com> (raw)
In-Reply-To: <20090112163201.GA26647@Krystal>

Mathieu Desnoyers wrote:
> * Zhaolei (zhaolei at cn.fujitsu.com) wrote:
>> * From: "Mathieu Desnoyers" <compudj@krystal.dyndns.org>
>>> * Zhaolei (zhaolei at cn.fujitsu.com) wrote:
>>>> * From: "Mathieu Desnoyers" <compudj@krystal.dyndns.org>
>>>>> * Zhaolei (zhaolei at cn.fujitsu.com) wrote:
>>>>>> Instrumentation of following panic and kexec related events are added:
>>>>>> panic
>>>>>> kernel_kexec
>>>>>> crash_kexec
>>>>>>
>>>>>> It is useful for build flight-recorder program based on lttng infrastructure.
>>>>>>
>>>>> Hrm, I'm wondering if these are events we are interested to trace or if
>>>>> you plan to use these tracepoints as hooks into the kernel to connect
>>>>> the tracer infrastructure to it ?
>>>> Hello, Mathieu
>>>>
>>>> IMHO, both.
>>>>
>>>> As a programmer who want to build  flight-recorder based on lttng infrastructure,
>>>> he can:
>>>> 1: use lttng trace, and get lttng's trace datas from kernel-dump file.
>>>> or
>>>> 2: use lttng's tracepoint, and record events himself.
>>>>
>>>> But as a lttng's programmer, we can make both way possible.
>>>>
>>>> What is your opinion?
>>>>
>>> Yes, I think having both is good. So we could add, separately :
>>>
>>> A hook in panic and kexec using include/linux/notifier.h so mechanisms
>>> other than tracers can connect their hook to it.
>>>
>>> Also add a tracepoint so tracers can use this as an event source.
>>>
>>> I would do both in separate patches though, because they have different
>>> purposes.
>> Hello, Mathieu
>>
>> Are you means you will do both in next version of lttng?
>> Thanks!
>>
> 
> Hi Zhaolei,
> 
> I won't create the patches myself because I don't see it as a priority
> (Linus said he would refuse any instrumentation patch before we get the
> data output mechanism into the kernel), but if someone provides patches

Hi, Mathieu,

You *forgot* one thing: we are lttng *users*, not only developers.
I don't think it's good that you just heard the God only.

lttng is used by her users at the end. User's need is one of the
first class things to concern.

> to add notifier feature to kexec and panic so we can plug LTTng into
> them to extract traces from a crashed kernel, I would be very interested
> to add this. OTOH, about the tracepoints, I am not convinced they are
> necessary for now, because we already instrument printk which logs some
> information on panic(). Maybe kexec would be better suited for
> instrumentation.

We need to know the time and other information that panic happened.
And output message is integrated in lttng with other messages.
I don't think it's bad idea which we use for a long time.

And this is a *key message*, event should be generated efficient/elegant.

Sorry for participated in this discuss with bad manners.

Thanks, Lai.

> 
> Also, it would be good to provide the LTTng probes for the tracepoints
> you add in a separate patch within the same patchset
> (ltt/probes/*-trace.c).
> 
> Thanks,
> 
> Mathieu
> 




  reply	other threads:[~2009-01-16  6:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18  3:01 [ltt-dev] [PATCH 0/2] Add tracepoint " Zhaolei
2008-12-18  3:02 ` [ltt-dev] [PATCH 2/1] tracepoints-panic Zhaolei
2008-12-18  4:14   ` Mathieu Desnoyers
2008-12-18  5:38     ` Zhaolei
2008-12-18  5:38       ` [ltt-dev] [PATCH v2] add tracepoints of panic and kexec Zhaolei
2008-12-18 18:47         ` Mathieu Desnoyers
2008-12-19  1:36           ` Zhaolei
2009-01-03 14:02             ` Mathieu Desnoyers
2009-01-12  5:55               ` Zhaolei
2009-01-12 16:32                 ` Mathieu Desnoyers
2009-01-16  6:47                   ` Lai Jiangshan [this message]
2009-01-16 15:43                     ` Mathieu Desnoyers
2009-01-19  6:29                       ` KOSAKI Motohiro
2009-01-20  2:08                         ` Mathieu Desnoyers
2009-02-19  4:14             ` Mathieu Desnoyers
2009-02-19  5:31               ` Zhaolei
2009-02-19  5:46                 ` Mathieu Desnoyers
2009-02-19  6:13                   ` Mathieu Desnoyers
2009-02-19  6:25                     ` Zhaolei
2008-12-30  1:52           ` [ltt-dev] [PATCH v3 0/1] " Zhaolei
2008-12-30  1:53             ` [ltt-dev] [PATCH v3 1/1] " Zhaolei
2009-01-03 13:45               ` Mathieu Desnoyers
2008-12-18  3:03 ` [ltt-dev] [PATCH 2/2] tracepoints-kexec Zhaolei
2008-12-18  4:19   ` Mathieu Desnoyers

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=49702D66.80609@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.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