From: Jim Nelson <james4765@verizon.net>
To: Peter STIEGLITZ <peter.stieglitz@st.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Inter-module communication
Date: Fri, 12 Nov 2004 22:05:46 -0500 [thread overview]
Message-ID: <41957A0A.5040709@verizon.net> (raw)
In-Reply-To: <000001c4c8d1$82a92620$340d81a4@benin>
Peter STIEGLITZ wrote:
> Hi folks,
> I have a requirement using 2.6 to notify more than one kernel module following the receipt of an interrupt.
>
> I've heard of module unloading becoming a problem with other modules assuming they are still there.
>
> What do people think is the best approach?
>
> Regards
> Pete
>
If this is going to be a suite of drivers, I'd probably write a function into each
module that is called whenever an interrupt of interest is called. Then, in the
bottom half of the actual interrupt handler, I'd iterate over an array of those
functions, letting each module know that an interrupt had occurred.
You'll probably need an IPC-like module to handle the message-passing interface
(unless a feature like this is already built into the kernel - anyone know?).
Interesting problem - a microkernel would make this a little easier, but I don't
think that there is a generic message-passing capability built into the Linux kernel.
There are some nasty obstacles to overcome - especially if you want to use it w/
SMP or with the real-time preemptive system in development. Unfortunately, that's
where my kernel-hacking skills run dry. Ask me again in a year or so - I could
probably give you a better answer then :)
Jim
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-11-13 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 16:05 Inter-module communication Peter STIEGLITZ
2004-11-13 3:05 ` Jim Nelson [this message]
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=41957A0A.5040709@verizon.net \
--to=james4765@verizon.net \
--cc=linux-newbie@vger.kernel.org \
--cc=peter.stieglitz@st.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