From: Werner Almesberger <wa@almesberger.net>
To: "Vamsi Krishna S ." <vamsi@in.ibm.com>
Cc: Richard J Moore <richardj_moore@uk.ibm.com>,
Rob Landley <landley@trommello.org>,
linux-kernel@vger.kernel.org,
S Vamsikrishna <vamsi_krishna@in.ibm.com>
Subject: Re: 2.4 Ready list - Kernel Hooks
Date: Thu, 24 Oct 2002 14:22:00 -0300 [thread overview]
Message-ID: <20021024142200.L1421@almesberger.net> (raw)
In-Reply-To: <20021024130835.A30737@in.ibm.com>; from vamsi@in.ibm.com on Thu, Oct 24, 2002 at 01:08:35PM +0530
Vamsi Krishna S . wrote:
> So, hooks are designed, placed at well thought-out locations.
> Probes OTOH are mostly ad-hoc.
Yes, my point was that the same (general) mechanism should be
suitable for both types of use. However, ...
>> [kd]probes. I haven't looked at that part yet. Do you have the
>> infrastructure for this ?
>>
> No, returning from caller will be much harder with [kd]probes.
... this seems to kill my grand unified hook/probe theory :-(
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2002-10-24 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 16:47 2.4 Ready list - Kernel Hooks Richard J Moore
2002-10-23 19:50 ` Werner Almesberger
2002-10-24 7:38 ` Vamsi Krishna S .
2002-10-24 17:22 ` Werner Almesberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 16:38 Richard J Moore
2002-10-24 17:02 ` Greg KH
2002-10-23 8:10 Richard J Moore
2002-10-23 17:09 ` Greg KH
2002-10-22 23:09 Richard J Moore
2002-10-22 23:54 ` Greg KH
2002-10-23 15:28 ` Werner Almesberger
2002-10-23 16:21 ` Karim Yaghmour
2002-10-21 12:24 Richard J Moore
2002-10-22 21:02 ` Werner Almesberger
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=20021024142200.L1421@almesberger.net \
--to=wa@almesberger.net \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardj_moore@uk.ibm.com \
--cc=vamsi@in.ibm.com \
--cc=vamsi_krishna@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.