public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Arkady <arkady.miasnikov@gmail.com>
To: David Smith <dsmith@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: context[2] stuck: (null)
Date: Wed, 12 Jul 2017 15:39:00 -0000	[thread overview]
Message-ID: <CANA-60rupXm3w3ohCsAL1B0V2gKeV0i2v_dEfZBwyAmx0bd+gA@mail.gmail.com> (raw)
In-Reply-To: <CANA-60rz4vDc8cJkbWHk_GqD=mAz-JcTBLuHoPeU124aTsW+sg@mail.gmail.com>

On Wed, Jul 12, 2017 at 5:40 PM, Arkady <arkady.miasnikov@gmail.com> wrote:
> On Wed, Jul 12, 2017 at 4:55 PM, David Smith <dsmith@redhat.com> wrote:
>> On Wed, Jul 12, 2017 at 8:16 AM, Arkady <arkady.miasnikov@gmail.com> wrote:
>>> My goal is to allocate the shared memory - one or more large (100s of
>>> MBs) vzallocs,
>>> add a dozen files to the sysfs and debugfs.
>>
>> Note that systemtap already has procfs 'probes', which create procfs files.
>>
>
> procfs API has limitations and inconveniences.
>
>> If we wanted to include this functionality with systemtap, we'd have
>> to generalize this a bit and make it less domain specific. Can you
>> think of a script language extension that would express what you are
>> trying to do here?
>>
>
> I would like to have an Initialization probe which allows use of blocking APIs.

.... for example probe begin_interruptable {}  and probe end_interruptable {}

>
>> --
>> David Smith
>> Principal Software Engineer
>> Red Hat

  reply	other threads:[~2017-07-12 15:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 15:16 Arkady
2017-07-11  6:25 ` Arkady
2017-07-11  6:47   ` Arkady
2017-07-11 10:31     ` Arkady
2017-07-12 13:01       ` David Smith
2017-07-12 12:58     ` David Smith
2017-07-12 13:16       ` Arkady
2017-07-12 13:55         ` David Smith
2017-07-12 14:41           ` Arkady
2017-07-12 15:39             ` Arkady [this message]
2017-07-14 13:44               ` Arkady
2017-07-14 15:16               ` David Smith
2017-07-14 16:38                 ` Arkady
2017-07-14 17:40                   ` Arkady
2017-07-16 16:33                     ` Arkady

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=CANA-60rupXm3w3ohCsAL1B0V2gKeV0i2v_dEfZBwyAmx0bd+gA@mail.gmail.com \
    --to=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).