public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: "Jason Yeh" <jason.yeh@amd.com>
Cc: systemtap@sources.redhat.com
Subject: Re: resolving probe point context_switch
Date: Thu, 12 Oct 2006 20:11:00 -0000	[thread overview]
Message-ID: <y0modshb8he.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <452E8704.1020105@amd.com>

"Jason Yeh" <jason.yeh@amd.com> writes:

> [...]  I have been trying to get Systemtap to place probe in the
> scheduler and hoping to experiment using Systemtap to emulate
> certain behavior of Perfmon2 similar to what Frank mentioned in the
> email titled "Model-Specific Register".

Thanks for giving that a try!

> [...]
> while: resolving probe point kernel.inline("context_switch")
> while: resolving probe point kernel.inline("finish_task_switch")
> while: resolving probe point kernel.inline("pull_task")
> while: resolving probe point kernel.inline("idle_balance")

We have some known weaknesses probing inline functions, which we may
be able to improve significantly.  In the mean time, something coarser
might have to do:

      probe kernel.statement("schedule") { /* leaving tid() on cpu() */ }
      probe kernel.function("schedule").return { /* resuming tid() on cpu() */ }

FWIW, the scheduler is one of the spots that would benefit most from
static instrumentation markers.


- FChE

      reply	other threads:[~2006-10-12 20:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12 15:24 LKET tests Frank Ch. Eigler
2006-10-12 18:10 ` resolving probe point context_switch Jason Yeh
2006-10-12 20:11   ` Frank Ch. Eigler [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=y0modshb8he.fsf@ton.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=jason.yeh@amd.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).