public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Shiyao Ma <i@introo.me>
To: David Smith <dsmith@redhat.com>, Arkady <arkady.miasnikov@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: Is it ok to insert a module multiple times with staprun?
Date: Fri, 31 Mar 2017 15:46:00 -0000	[thread overview]
Message-ID: <CAJQX3DydfagGekve1SOdN+biBfDLBWhjv+Ry-aRugqvktqqE9A@mail.gmail.com> (raw)
In-Reply-To: <CAKFOr-bzF8Tb2Wtf=Q=761JgmLaVaexOZy8jW+V4h-2jkOqw6g@mail.gmail.com>

Hi,

Just checked the system() command is async, though.

but I got the picture here.

Thanks.

On Fri, Mar 31, 2017 at 11:40 PM, David Smith <dsmith@redhat.com> wrote:
> On Fri, Mar 31, 2017 at 9:50 AM, David Smith <dsmith@redhat.com> wrote:
>> On Thu, Mar 30, 2017 at 10:51 PM, Shiyao Ma <i@introo.me> wrote:
>
> OK, I had another sneaky thought here. You could use the system()
> function to copy the config file to the /proc file. I haven't had time
> to test this, but in theory something like this should work:
>
> ====
> global config_done
>
> probe procfs.write("config")
> {
>     # process $value here
>    config_done = 1
> }
>
> probe kernel.function("vfs_read") if (config_done)
> {
>    # real processing here...
> }
>
> probe begin
> {
>    system(sprintf("cat config > /proc/systemtap/%s/config", module_name()))
> }
> ====
>
> --
> David Smith
> dsmith@redhat.com
> Red Hat
> http://www.redhat.com
> 256.217.0141 (direct)
> 256.837.0057 (fax)

  reply	other threads:[~2017-03-31 15:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30  4:41 Shiyao Ma
2017-03-30  5:40 ` Arkady
     [not found]   ` <e7f616ba-eb90-47ee-b784-ea02fdf519ff@Spark>
2017-03-30  8:22     ` Arkady
2017-03-30 14:53       ` David Smith
2017-03-31  3:51         ` Shiyao Ma
2017-03-31  4:08           ` Arkady
2017-03-31 14:50           ` David Smith
2017-03-31 15:40             ` David Smith
2017-03-31 15:46               ` Shiyao Ma [this message]
2017-04-01  6:15               ` Shiyao Ma

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=CAJQX3DydfagGekve1SOdN+biBfDLBWhjv+Ry-aRugqvktqqE9A@mail.gmail.com \
    --to=i@introo.me \
    --cc=arkady.miasnikov@gmail.com \
    --cc=dsmith@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).