From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/18848] New: new --monitor option
Date: Tue, 18 Aug 2015 13:44:00 -0000 [thread overview]
Message-ID: <bug-18848-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18848
Bug ID: 18848
Summary: new --monitor option
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
As a part of the interactive-systemtap effort, we'd like to have a way of
compiling stap modules so that they can report on their own status, and give a
way to control them from the outside.
For example, a new option "stap --monitor" could emit extra code into the
module, so that:
- it presents a procfs interface by which stats like this are available:
- module name, invoker uid, sizes (as per startup dmesg)
- number of warnings, errors; maybe text of recent errors
- list of global variables (incl. array sizes)
- abbreviated list of probes (incl. hit count/times as per stap -t)
- it presents another procfs interface by which control may be exercised:
- to disable or enable probes (as if by hidden on-the-fly control variables)
- to reset the global variables (so as to start the script anew)
- to exit the script
Then the stapio program can connect to those two proc interfaces, poll the
former to display, map keyboard inputs for sending to the other. (The stap
--interactive front-end can later also do the same.)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-08-18 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 13:44 fche at redhat dot com [this message]
2015-08-18 14:39 ` [Bug runtime/18848] " dsmith at redhat dot com
2015-09-09 18:14 ` flu at redhat dot com
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=bug-18848-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).