From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "William Cohen" <wcohen@redhat.com>
Cc: <systemtap@sourceware.org>
Subject: RE: Summary of nightly testing 20061016
Date: Mon, 16 Oct 2006 17:54:00 -0000 [thread overview]
Message-ID: <C56DB814FAA30B418C75310AC4BB279DC4CE17@scsmsx413.amr.corp.intel.com> (raw)
On Monday, October 16, 2006 8:05 AM, William Cohen wrote:
> The timers.stp probe didn't register on FC5 i686 machine It failed
> with rc=-16, "Device or resource busy" because oprofile was already
> using the timer. So this means that only one probe could be using the
> timer mechanism, and no concurrent use?
For the plain timers, concurrent use is fine -- it's only a problem for
timer.profile. This is because of an API change that happened in
2.6.10. Previously, the profile timer was accessed with
register_profile_notifier, which used a notifier_block (allowing
unlimited registrants). In 2.6.10 it switched to register_timer_hook,
which uses a single pointer to store the callback (allowing only one
registrant).
Probably someone figured that oprofile was the only one that would ever
use the timer profiler, so this change was an "optimization". It does
reduce the work for making the callback, but the functionality is more
limited.
Josh
next reply other threads:[~2006-10-16 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 17:54 Stone, Joshua I [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-16 15:05 William Cohen
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=C56DB814FAA30B418C75310AC4BB279DC4CE17@scsmsx413.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=systemtap@sourceware.org \
--cc=wcohen@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).