public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Josh Stone <jistone@redhat.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: Dave Brolley <brolley@redhat.com>, systemtap@sources.redhat.com
Subject: Re: Does This Probe Make Sense?
Date: Tue, 06 Sep 2011 17:32:00 -0000	[thread overview]
Message-ID: <4E6649C0.2030607@redhat.com> (raw)
In-Reply-To: <1315321500.3895.41.camel@springer.wildebeest.org>

On 09/06/2011 08:04 AM, Mark Wielaard wrote:
>> So IMO, get rid of the .function(NUM).inline binding, and make sure that
>> addresses in an inline still reach out to the containing .call.
> 
> What do you mean by that last statement about "reach out"?

Perhaps "reach up" would have been better, as in up the die hierarchy. I
meant that given an address within an inline instance, we should still
get a probe on the containing function.

Josh

      reply	other threads:[~2011-09-06 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 15:38 Dave Brolley
2011-08-30 16:38 ` Josh Stone
2011-09-06 15:05   ` Mark Wielaard
2011-09-06 17:32     ` Josh Stone [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=4E6649C0.2030607@redhat.com \
    --to=jistone@redhat.com \
    --cc=brolley@redhat.com \
    --cc=mjw@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).