public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "Martin Hunt" <hunt@redhat.com>, "Frank Ch. Eigler" <fche@redhat.com>
Cc: <systemtap@sources.redhat.com>
Subject: RE: MAXACTION exceeded error while using systemtap
Date: Thu, 08 Dec 2005 17:50:00 -0000	[thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC05CE5F78@scsmsx403.amr.corp.intel.com> (raw)

Martin Hunt wrote:
> Because timer probes can run in process context which means they
> sleep, can be scheduled, take as long as they want? Whereas a kprobe
> might be in the middle of a task switch.

I just want to point out that this is not true of the timer.profile
variety, which runs (by necessity) in a true interrupt context.

Josh

             reply	other threads:[~2005-12-08 17:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 17:50 Stone, Joshua I [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-06 21:56 Stone, Joshua I
2005-12-06 22:11 ` Frank Ch. Eigler
2005-12-07 20:53   ` Martin Hunt
2005-12-07 21:09     ` Frank Ch. Eigler
2005-12-07 22:29       ` Martin Hunt
2005-12-07 23:07         ` Frank Ch. Eigler
2005-12-08  8:55           ` Martin Hunt
2005-12-08 12:52             ` James Dickens
2005-12-08 13:57               ` Frank Ch. Eigler
2005-12-28 19:06                 ` Marcelo Tosatti
2005-12-28 20:12                   ` Tom Zanussi
2005-12-28 20:38                     ` Marcelo Tosatti
2005-12-28 21:13                   ` Frank Ch. Eigler
2005-12-08 13:37             ` Frank Ch. Eigler
2005-12-06 20:41 Stone, Joshua I
2005-12-06 20:55 ` Frank Ch. Eigler
2005-12-06 16:40 Badari Pulavarty
2005-12-06 16:59 ` Frank Ch. Eigler
2005-12-07  1:10   ` Badari Pulavarty
2005-12-07 15:21     ` William Cohen
2005-12-07 16:37       ` Badari Pulavarty
2005-12-06 17:01 ` Hien Nguyen

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=CBDB88BFD06F7F408399DBCF8776B3DC05CE5F78@scsmsx403.amr.corp.intel.com \
    --to=joshua.i.stone@intel.com \
    --cc=fche@redhat.com \
    --cc=hunt@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).