From: Jeremy Jackson <jerj@coplanar.net>
To: george anzinger <george@mvista.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Event tools, do they exist
Date: Wed, 25 Apr 2001 11:36:03 -0400 [thread overview]
Message-ID: <3AE6EEE3.ACE4F18F@coplanar.net> (raw)
In-Reply-To: <3AE61FF2.DF9849BB@mvista.com>
I think all of this has been done... you should check out
the Linux Trace Toolkit.
george anzinger wrote:
> This is an attempt to look in the wheel locker.
>
> I need a simple event sub system for use in the kernel. I envision at
> least two types of events: the history event and the timing event.
>
> The timing event would keep track of start/stop times by class. If, for
> example, I wanted to know how much time the kernel spends doing the
> recalc in schedule() I would put and event start in front of it and an
> end at the other end. The sub system would note the first event time
> and the cumulative time between all starts and stops on the same event.
> When reported by /proc/ it would give the total event time, the elapsed
> time and the % of processor time for each of the possibly several
> classes.
>
> The history event would record each events time, location, data1,
> data2. It would keep N of these (the last N) and report M (M=<N) via
> /proc/. This list should also be kept in a format that a simple
> debugger can easily examine.
>
> Somebody must have written these routines and have them in their
> library. Sure would help if I could have a peek.
next prev parent reply other threads:[~2001-04-25 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 0:53 Event tools, do they exist george anzinger
2001-04-25 3:02 ` Andrew Morton
2001-04-25 15:36 ` Jeremy Jackson [this message]
2001-04-26 8:54 ` Karim Yaghmour
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=3AE6EEE3.ACE4F18F@coplanar.net \
--to=jerj@coplanar.net \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
/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.