From: Stephen Wille Padnos <stephenwp@adelphia.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Exporting new functions from kernel 2.2.14
Date: Tue, 05 Jun 2001 08:54:31 -0700 [thread overview]
Message-ID: <3B1D00B7.168B52D1@adelphia.net> (raw)
Hello, all.
I am writing a pseudo-realtime control system, based on kernel 2.2.14.
The only RT-like task needs to hang off the timer IRQ. I am using
techniques like those in the book "Linux Kernel Internals", by Beck, et
al..
The patches in that book won't apply (they are for 2.1.24 or lower),
plus I want a somewaht different functionality, which brings me to my
question: How can I get (modversions-enabled) functions exported from
arch/i386/kernel/irq.c?
I see in /proc/ksyms that there are some functions exported from there
({enable,disable}_irq, probe_irq_{on,off}, etc.), and they have correct
looking versions.
When I add my new finctions to i386ksyms.c:
EXPORT_SYMBOL(grab_timer_interrupt);
EXPORT_SYMBOL(release_timer_interrupt);
I get names like
grab_timer_interrupt_R__ver_grab_timer_interrupt
release_timer_interrupt_R__ver_release_timer_interrupt
instead of
local_irq_count_R4d40375f
Additionally, when I make a dummy module (a la Alessandro Rubini's
"Hello" module in "Linux Device Drivers"), I get the following warning:
control.c:31: warning: implicit declaration of function
`printk_R1b7d4074'
The module seems to work (it printk's "module loaded" on load and
"module unloaded" on unload), but I suspect that this is because I am
printk()-ing unformatted text strings - only one parameter gets sent.
So, I obviously have missed some basics about:
a) versioning,
b) exporting symbols, and
c) modules.
could soemone please enlighten me, or direct me along the path of
enlightenment :)
Thanks
- Steve
next reply other threads:[~2001-06-05 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 15:54 Stephen Wille Padnos [this message]
2001-06-05 13:10 ` Exporting new functions from kernel 2.2.14 Arthur Naseef
2001-06-05 13:24 ` Keith Owens
2001-06-05 13:25 ` Arthur Naseef
2001-06-05 17:09 ` Stephen Wille Padnos
2001-06-05 17:32 ` Stephen Wille Padnos
2001-06-05 14:59 ` Keith Owens
2001-06-05 13:23 ` Keith Owens
2001-06-05 17:10 ` Stephen Wille Padnos
2001-06-05 14:22 ` Keith Owens
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=3B1D00B7.168B52D1@adelphia.net \
--to=stephenwp@adelphia.net \
--cc=linux-kernel@vger.kernel.org \
/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