From: john stultz <johnstul@us.ibm.com>
To: Stas Sergeev <stsp@aknet.ru>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [rfc][patch] API for timer hooks
Date: Mon, 15 Aug 2005 10:19:13 -0700 [thread overview]
Message-ID: <1124126354.8630.3.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <42FDF744.2070205@aknet.ru>
On Sat, 2005-08-13 at 17:36 +0400, Stas Sergeev wrote:
> Hello.
>
> Right now it seems like the only interface
> for registering the timer hooks is that one
> of kernel/profile.c, and it is very limited.
> The arch-specific timer hooks are provided
> in an arch-specific headers as a static
> functions.
> Since my driver needs the timer hook, I
> thought it might be a good idea to add an
> API for registering the timer hooks.
> The attached patch adds such an API and
> converts all the relevant places to use it.
> I changed oprofile to use it, and also
> converted the arch-specific hooks, which
> looks like a fair cleanup.
>
> The API allows to register, unregister
> and grab the timer hook. The grabbing
> hook will always be executed first, and
> can decide to prevent an execution of
> the rest ones. The hook can have the
> "run_always" flag set, in which case it
> won't be bypassed, regardless of the
> grabbing hook.
>
> Does such an API look viable?
> As usual, it is needed for the PC-Speaker
> PCM driver that is currently in an ALSA CVS,
> awaiting for the proper interface to appear
> in the kernel.
Interesting. Could you explain why the soft-timer interface doesn't
suffice?
thanks
-john
next prev parent reply other threads:[~2005-08-15 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 13:36 Stas Sergeev
2005-08-15 17:19 ` john stultz [this message]
2005-08-16 20:21 ` Stas Sergeev
2005-08-16 22:24 ` Nish Aravamudan
2005-08-17 16:10 ` Stas Sergeev
2005-08-17 2:09 ` Lee Revell
2005-08-17 16:21 ` Stas Sergeev
2005-08-17 16:40 ` Lee Revell
2005-08-17 17:41 ` Stas Sergeev
2005-08-17 23:16 ` Lee Revell
2005-08-18 16:59 ` Stas Sergeev
2005-08-18 17:07 ` Lee Revell
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=1124126354.8630.3.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
/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
all inboxes | Powered by JetHome®