public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Maynard Johnson <maynardj@us.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: Proposed systemtap access to perfmon hardware
Date: Wed, 22 Mar 2006 18:30:00 -0000	[thread overview]
Message-ID: <y0modzye4z6.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <4420C5A2.9060702@us.ibm.com>


maynardj wrote:

> [...]

Several aspects of the script interface to the performance counters
was changed later in this thread: please check that too.

> >The performance monitoring events are specified in strings. The
> >information at the very least include the event name being monitored
> [...]
> Should the event name be the native event name for the arch?  Or some
> generic name that is mapped to a native name by some mechanism?  Or
> either (as in PAPI)?

It may be sufficient to use systemtap's general abstraction mechanisms
to map between generic and native event names, in much the same way as
the system-call tapset defines generic names ("syscall.read") in terms
of native functions ("kernel.function(...)").  This aliasing widget
may need some extension in order to deal with parameters or partial
matches; we'll know after someone constructs an informal
generic<->native event name dictionary.

- FChE

  parent reply	other threads:[~2006-03-22 18:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 16:24 William Cohen
2006-03-15 22:34 ` Frank Ch. Eigler
2006-03-17 16:20   ` William Cohen
2006-03-17 17:10     ` Bill Rugolsky Jr.
2006-03-17 17:34     ` Frank Ch. Eigler
2006-03-17 20:26       ` William Cohen
2006-03-20 17:27         ` Frank Ch. Eigler
2006-03-22  3:34 ` Maynard Johnson
2006-03-22 18:02   ` William Cohen
2006-03-22 22:16     ` Maynard Johnson
2006-03-22 18:30   ` Frank Ch. Eigler [this message]
2006-03-22 19:09 Stone, Joshua I
2006-03-22 20:04 ` Frank Ch. Eigler
2006-03-22 23:23 Stone, Joshua I
2006-03-22 23:46 Stone, Joshua I
2006-03-23 12:54 ` Maynard Johnson
2006-03-23 14:46   ` William Cohen
2006-03-23 17:09 Stone, Joshua I

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=y0modzye4z6.fsf@ton.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=maynardj@us.ibm.com \
    --cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).