From: "Arthur Naseef" <arthur.naseef@ariel.com>
To: "Stephen Wille Padnos" <stephenwp@adelphia.net>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: RE: Exporting new functions from kernel 2.2.14
Date: Tue, 5 Jun 2001 09:10:56 -0400 [thread overview]
Message-ID: <OIBBKHIAILDFLNOGGFMNOEHLCBAA.arthur.naseef@ariel.com> (raw)
In-Reply-To: <3B1D00B7.168B52D1@adelphia.net>
Steve:
I still have not figured out the magic that creates the .ver files which
would resolve your concern with the symbol versions, but I do know that
you can edit the .ver file yourself (under /usr/src/linux/include/modules/)
and add entries. This will eliminate the funny versioning, as in:
grab_timer_interrupt_R__ver_grab_timer_interrupt
You can pick a hash value to use. For example, you might add the following:
#define __ver_grab_timer_interrupt a1b2c3d4
#define grab_timer_interrupt _set_ver(grab_timer_interrupt)
As far as the printk() warning, you need to make sure your module code
includes the right header files. In this case, I believe you need to grab
<linux/kernel.h> after including <linux/module.h>.
I hope this helps.
-art
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Stephen Wille
> Padnos
> Sent: Tuesday, June 05, 2001 11:55 AM
> To: Linux Kernel
> Subject: Exporting new functions from kernel 2.2.14
>
>
> 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
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
next prev parent reply other threads:[~2001-06-05 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 15:54 Stephen Wille Padnos
2001-06-05 13:10 ` Arthur Naseef [this message]
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=OIBBKHIAILDFLNOGGFMNOEHLCBAA.arthur.naseef@ariel.com \
--to=arthur.naseef@ariel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stephenwp@adelphia.net \
/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®