This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: context[2] stuck: (null)
- From: Arkady <arkady dot miasnikov at gmail dot com>
- To: David Smith <dsmith at redhat dot com>
- Cc: systemtap at sourceware dot org
- Date: Wed, 12 Jul 2017 17:40:51 +0300
- Subject: Re: context[2] stuck: (null)
- Authentication-results: sourceware.org; auth=none
- References: <CANA-60q25-tnw72LjrtgMaavsE=VCee4-66fkOHbKBAHWSNqDA@mail.gmail.com> <CANA-60pAhrCXkzkNS5sY_Cypd-_ky=zfHmxHi-dj06QFkrOQAg@mail.gmail.com> <CANA-60rKy7uxpeF_zSV=nMwGO_oRp_rNHnt-PrWRzG4QivKsrQ@mail.gmail.com> <CAKFOr-ZzbumvHnZuZ3cHY5ZVG7uY9wnR4Cft3ghjE+FuSJTHNg@mail.gmail.com> <CANA-60rDmaWUKcPgy=dsShfQLnyG-nWQCXunffrNTBKu0AJTpw@mail.gmail.com> <CAKFOr-YOxRz=MssmT0R_j+Qp2fb2UEe3oKuPrsCa1xVa5ttUzw@mail.gmail.com>
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.
>> Some of the things I am doing involve kernel APIs which block. I was thinking
>> about the following options
>> The last option - take the initialization offline - a tasklet could do
>> the work. It
>> was longer to develop and the hour was late.
>
> 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.
> --
> David Smith
> Principal Software Engineer
> Red Hat