From: Mats Liljegren <mats.liljegren@enea.com>
To: duzhiping <duzhiping.du@huawei.com>
Cc: <rostedt@goodmis.org>, <mingo@redhat.com>,
<linux-kernel@vger.kernel.org>, <wangnan0@huawei.com>
Subject: Re: itrace: An interrupts tracing tool
Date: Mon, 22 Sep 2014 10:04:23 +0200 [thread overview]
Message-ID: <20140922100423.410e3644@mats-desktop> (raw)
In-Reply-To: <541F990F.7030806@huawei.com>
On Mon, 22 Sep 2014 11:35:43 +0800
duzhiping <duzhiping.du@huawei.com> wrote:
> Many functions depends on interrupts in Linux system, when the
> interrupts occur an error, it may cause fatal problem.
>
> Then, we should record their trace when interrupts in and out. The
> recorded information could help us analyze interrupts errors.
>
> Itrace is such an interrupts trace tool we have developed, it
> provides config interface and trace information through "procfs".
>
> Do you think it has the value to upstream?
Where can I look at the code?
What makes it different from existing tools, e.g. ftrace?
/Mats
next prev parent reply other threads:[~2014-09-22 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 3:35 itrace: An interrupts tracing tool duzhiping
2014-09-22 8:04 ` Mats Liljegren [this message]
2014-09-22 12:18 ` Steven Rostedt
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=20140922100423.410e3644@mats-desktop \
--to=mats.liljegren@enea.com \
--cc=duzhiping.du@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=wangnan0@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.