All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Ratkin <kratkin@egartech.com>
To: Michael Rozhavsky <mrozhavsky@opticalaccess.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Call kernel function from module
Date: Wed, 31 Oct 2001 14:46:43 +0300	[thread overview]
Message-ID: <3BDFE4A3.309D66CE@egartech.com> (raw)
In-Reply-To: <01103112311302.00794@nemo> <3BDFD866.E6E997CC@egartech.com> <20011031133438.O24143@opticalaccess.com>


Michael Rozhavsky wrote:
> 
> [snip]
> >
> > Hi! Could somebody help me? I added several functions (not sys calls) to
> > kernel as hardcoded part. Then I write modules which will be call these
> > functions. But when I load module insmod says me 'can't resolve symbol
> > my_func_name'.
> > I exported all my functions in netsyms.c file. Do you know how I can see
> > my function?
> 
> use EXPORT_SYMBOL macro from include/module.h
Yes. I added it in netsyms.c and I see all my functions in System.map
file. (into ksyms too)

#ifdef CONFIG_BATON
#include <linux/baton.h>
EXPORT_SYMBOL(baton_init);
EXPORT_SYMBOL(baton_register_hook);
EXPORT_SYMBOL(baton_unregister_hook);
#endif

> 
> >
> > Regards,
> > Niktar.
> > -
> > 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/
> Best regards.
> 
> --
>    Michael Rozhavsky                    Tel:    +972-4-9936248
>    mrozhavsky@opticalaccess.com         Fax:    +972-4-9890564
>    Optical Access
>    Senior Software Engineer             www.opticalaccess.com

      reply	other threads:[~2001-10-31 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31 12:31 [PATCH] setup.S: fix for BIOS/DOS not reporting ext mem size vda
2001-10-31 10:54 ` Call kernel function from module Kirill Ratkin
2001-10-31 11:34   ` Michael Rozhavsky
2001-10-31 11:46     ` Kirill Ratkin [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=3BDFE4A3.309D66CE@egartech.com \
    --to=kratkin@egartech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrozhavsky@opticalaccess.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.