public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karym@opersys.com>
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: Thu, 26 Apr 2001 04:54:51 -0400	[thread overview]
Message-ID: <3AE7E25B.6E81783E@opersys.com> (raw)
In-Reply-To: <3AE61FF2.DF9849BB@mvista.com>


Hellor George,

As others have suggested, you can do what you are asking for using LTT
(http://www.opersys.com/LTT).

Specifically, you may want to use the event allocation capabilities.
This will enable you to add your own events and view these as part
of the trace.

By the way, there are mailing lists for LTT if you're interested to
make a contribution.

Cheers,

Karim

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.
> 
> George
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
===================================================
                 Karim Yaghmour
               karym@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

      parent reply	other threads:[~2001-04-26  8:48 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
2001-04-26  8:54 ` Karim Yaghmour [this message]

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=3AE7E25B.6E81783E@opersys.com \
    --to=karym@opersys.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox