public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Lebon <jlebon@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: systemtap@sourceware.org, fche@redhat.com
Subject: Re: [PATCH v2 0/3] initscript: add support for uprobes scripts
Date: Wed, 03 Sep 2014 23:01:00 -0000	[thread overview]
Message-ID: <1623394325.37775.1409785309600.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20140903124615.GK28095@stefanha-thinkpad.redhat.com>

Hi Stefan,

I've pushed the original series for now (v2).
Thanks for the contribution! :)

I've added a follow-up commit to make use of --save-uprobes rather
than -u so that we don't block the stap -u option while remaining
compatible with the idea we mentioned.

BTW, while testing, I've noticed that --save-uprobes only has an
effect if uprobes.ko was not already built and cached in a previous
run. Have you encountered that as well?

We may need to tweak the buildrun.cxx logic a bit if that's the
case.

  reply	other threads:[~2014-09-03 23:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 13:25 Stefan Hajnoczi
2014-08-11 13:25 ` [PATCH v2 1/3] stap: add --save-uprobes Stefan Hajnoczi
2014-08-11 13:25 ` [PATCH v2 3/3] initscript: allow scripts to load uprobes Stefan Hajnoczi
2014-08-11 13:25 ` [PATCH v2 2/3] initscript: copy uprobes.ko to cache directory Stefan Hajnoczi
2014-09-01 12:15 ` [PATCH v2 0/3] initscript: add support for uprobes scripts Stefan Hajnoczi
2014-09-02 15:03   ` Jonathan Lebon
2014-09-03 12:46     ` Stefan Hajnoczi
2014-09-03 23:01       ` Jonathan Lebon [this message]
2014-09-03 23:22         ` Josh Stone
2014-09-03 23:44           ` [PATCH] Remove systemtap_session::built_uprobes Josh Stone
2014-09-04 11:13             ` Stefan Hajnoczi
2014-09-04 15:20             ` Jonathan Lebon

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=1623394325.37775.1409785309600.JavaMail.zimbra@redhat.com \
    --to=jlebon@redhat.com \
    --cc=fche@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).