From: Arjan van de Ven <arjan@infradead.org>
To: S <talk2sumit@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux prg <linux-c-programming@vger.kernel.org>
Subject: Re: LKM function call on kernel function call?
Date: Tue, 05 Jul 2005 10:38:26 +0200 [thread overview]
Message-ID: <1120552708.3180.29.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1458d9610507050123124d6cb@mail.gmail.com>
On Tue, 2005-07-05 at 16:23 +0800, S wrote:
> Is it possible to code a loadable module having function1(), which
> would be called, everytime a particular function of the kernel is
> called? If not, atleast a way this could be done without re-compiling
> the whole kernel and rebooting the system?
why don't you want to compile the whole kernel ? You have the source
code and it for sure is the easiest way to add this (debug?) hack...
next prev parent reply other threads:[~2005-07-05 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 8:23 LKM function call on kernel function call? S
2005-07-05 8:38 ` Arjan van de Ven [this message]
2005-07-05 8:38 ` Frederik Deweerdt
2005-07-14 16:59 ` Daniel Bonekeeper
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=1120552708.3180.29.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-c-programming@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=talk2sumit@gmail.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 NNTP newsgroup(s).