public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "hunt at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/5194] New: IO problem on begin/end probes
Date: Thu, 18 Oct 2007 14:01:00 -0000	[thread overview]
Message-ID: <20071018140048.5194.hunt@redhat.com> (raw)

begin and end probes are now interruptible. This creates a problem with IO
because we use percpu buffers.

A possible solution would be to have the translator add a call to
smp_processor_id() to the probe prologue and modify the print functions to take
a cpu input instead of each calling smp_processor)id().

-- 
           Summary: IO problem on begin/end probes
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: critical
          Priority: P1
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: hunt at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=5194

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2007-10-18 14:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 14:01 hunt at redhat dot com [this message]
2007-10-18 14:10 ` [Bug runtime/5194] " fche at redhat dot com
2007-10-18 14:11 ` fche at redhat dot com
2007-10-18 14:25 ` hunt at redhat dot com
2007-10-18 15:19 ` fche at redhat dot com
2008-01-21 17:42 ` fche at redhat dot com
2008-01-21 17:56 ` hunt at redhat dot com
2008-01-21 18:13 ` [Bug runtime/5194] IO problem on begin/end probes; need fche at redhat dot com
2008-01-21 18:37 ` fche at redhat dot com
2008-01-29 16:40 ` fche at redhat dot com
2008-01-29 17:08 ` hunt 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=20071018140048.5194.hunt@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).