From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: <fche@redhat.com>
Cc: <systemtap@sources.redhat.com>
Subject: RE: Proposed systemtap access to perfmon hardware
Date: Wed, 22 Mar 2006 23:23:00 -0000 [thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC06BC0D54@scsmsx403.amr.corp.intel.com> (raw)
fche@redhat.com wrote:
> joshua wrote:
>> [...]
>>> If they are started by default, where exactly are they running?
>>> Beginning of begin probe? End of begin probe?
>>
>> I think the perfmon setup needs to happen before all begin probes, so
>> that the handle can be accessed within begin probes. [...]
>
> How important would that be? At this time, we don't provide any
> ordering guarantees amongst begin/end probes. If a begin probe would
> have to manipulate the handle, why not put that right into the
> perfctr.*.setup probe directly?
Perhaps it isn't that important - I didn't consider putting the work in
the ".setup" probe. This is fine as long as the setup probe has the
guarantee that the counters haven't started yet (regardless of its
position in the begin stage)
It might be nice to have a similar shutdown/cleanup/whatever probe that
guarantees that the counters have been stopped. This is superfluous if
we guarantee that the counters will be stopped before running any end
probes, but I haven't seen discussion on that point yet. We should also
define when the handle be invalidated - this could be at the conclusion
of the cleanup probe, if it exists, or after all end probes have
completed.
Josh
next reply other threads:[~2006-03-22 23:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 23:23 Stone, Joshua I [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 17:09 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-22 19:09 Stone, Joshua I
2006-03-22 20:04 ` Frank Ch. Eigler
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
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=CBDB88BFD06F7F408399DBCF8776B3DC06BC0D54@scsmsx403.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=fche@redhat.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).