From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2293] New: confirm preemption/interrupt blocking in systemtap probes
Date: Tue, 07 Feb 2006 17:14:00 -0000 [thread overview]
Message-ID: <20060207171449.2293.fche@redhat.com> (raw)
For each probe type supported in tapsets.cxx, confirm that the probe handlers
are run in an atomic manner: preemption + interrupts disabled.
This could tie in with bug #1884, by detecting whether we are already in an
interrupt context, and if so, reducing the MAXACTION budget for this probe hit.
--
Summary: confirm preemption/interrupt blocking in systemtap
probes
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=2293
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2006-02-07 17:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 17:14 fche at redhat dot com [this message]
2006-02-22 15:06 ` [Bug translator/2293] " fche at redhat dot com
2006-02-22 20:07 ` hunt at redhat dot com
2006-02-23 20:42 ` fche at redhat dot com
2006-02-27 17:32 ` hunt at redhat dot com
2006-02-27 18:56 ` disabled interrupts (Was bug #2293 Frank Ch. Eigler
2006-02-27 19:16 ` Martin Hunt
2006-02-27 20:01 ` Frank Ch. Eigler
2006-02-27 21:10 ` Martin Hunt
2006-03-29 7:06 ` [Bug translator/2293] confirm preemption/interrupt blocking in systemtap probes hunt at redhat dot com
2006-03-29 11:55 ` fche at redhat dot com
2006-03-29 18:05 ` Martin Hunt
2006-03-29 20:18 ` Frank Ch. Eigler
2006-05-05 16:09 ` Vara Prasad
2006-03-29 18:05 ` hunt at redhat dot com
2006-05-01 14:20 ` fche at redhat dot com
2006-05-05 16:10 ` prasadav at us dot ibm dot com
[not found] ` <20060505160951.1801.qmail@sourceware.org>
2006-05-05 16:38 ` Frank Ch. Eigler
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=20060207171449.2293.fche@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).