From: Martin Zwickel <martin.zwickel@technotrend.de>
To: sounak chakraborty <sounakrin@yahoo.co.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: architecture to implement communication between static kernel with dynamic module
Date: Thu, 3 Mar 2005 16:20:21 +0100 [thread overview]
Message-ID: <20050303162021.1839dad4@phoebee> (raw)
In-Reply-To: <20050303150901.71989.qmail@web53301.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
On Thu, 3 Mar 2005 15:09:01 +0000 (GMT)
sounak chakraborty <sounakrin@yahoo.co.in> bubbled:
> there is one my_own module
> which i will insert whenever i like through
> insmod.
> thus when the module is loaded it will create a proc
> file
>
> now i want to send the structure variable of
> task_struct
> i.e p to the module from the kernel at point when the
> execution passes
> through forking a new process i.e
> at the function do_fork() in fork.c in linux/kernel
> folder
>
> how to do this
>
> how can i call the module from that point (i.e in
> do_fork())
> and pass the task_struct *p as parameter to the module
>
> can i declare an arbitary name in fork.c of my module
> and compile the new kernel?
> i think i cannot since i am inserting a dynamic module
> to a static kernel executable
> and how does the kernel will know that this module
> will be attached later to it.
> it will show errors while compiling the new modified
> kernel
>
> can you help me ?
> what path i must take
> thanks
> sounak
>
Some kind of callback registration would do the job.
Regards,
Martin
--
MyExcuse:
Cow-tippers tipped a cow onto the server.
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-03 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 15:09 sounak chakraborty
2005-03-03 15:20 ` Martin Zwickel [this message]
2005-03-03 15:30 ` linux-os
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=20050303162021.1839dad4@phoebee \
--to=martin.zwickel@technotrend.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sounakrin@yahoo.co.in \
/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®