public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Martin Hunt <hunt@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: disabled interrupts (Was bug #2293
Date: Mon, 27 Feb 2006 21:10:00 -0000	[thread overview]
Message-ID: <1141074622.4794.54.camel@dragon> (raw)
In-Reply-To: <y0mirr0d11d.fsf@ton.toronto.redhat.com>

On Mon, 2006-02-27 at 15:01 -0500, Frank Ch. Eigler wrote:
> hunt wrote:
> 
> > The runtime calls probe_end(), and it used to know it was safe to sleep
> > while in probe_end(). So if it attempted to send data and no buffers
> > were available, it would sleep a bit (allowing stpd to precess the data)
> > and retry (up to a limit), thus ensuring 100% of the data got sent.
> 
> You must be referring to the msleep() loop in _stp_transport_send.
> Isn't that conditional on the "exit is pending" flag, which is set
> considerably earlier than the beginning of first "end" probe handler?

You are thinking of _stp_exit. _stp_exit_called is the flag we are
interested in.

int _stp_transport_write (void *data, int len)  
{
  /* when _stp_exit_called is set, we are in probe_exit() */
  /* and we can sleep */
  if (_stp_exit_called)
      return _stp_transport_send (STP_REALTIME_DATA, data, len);
  return _stp_write(STP_REALTIME_DATA, data, len);
}

From _stp_cleanup_and_exit()

	if (!_stp_exit_called) {
		_stp_exit_called = 1;
		probe_exit();

I'm going to move the _stp_exit_called to the other side of probe_exit()
for now. And I'm going to put a loop to wait on empty buffers before
probe_exit().  That's about all I can do.  


Martin

  reply	other threads:[~2006-02-27 21:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 17:14 [Bug translator/2293] New: confirm preemption/interrupt blocking in systemtap probes fche at redhat dot com
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 [this message]
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=1141074622.4794.54.camel@dragon \
    --to=hunt@redhat.com \
    --cc=fche@redhat.com \
    --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).