public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: John K <trv@freemail.gr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/ksyms and /proc/kallsyms relationship?
Date: Tue, 11 Nov 2008 00:02:11 +1100	[thread overview]
Message-ID: <18101.1226322131@ocs10w> (raw)
In-Reply-To: Your message of "Mon, 10 Nov 2008 03:00:16 +0200." <491787A0.5050901@freemail.gr>

On Mon, 10 Nov 2008 03:00:16 +0200, 
John K <trv@freemail.gr> wrote:
>In kernel 2.4, there was a /proc/ksyms file. This file, if I understand
>correctly, was a method to access the kernel's public symbol table. What
>was displayed had all the public kernel's symbols (variables,
>functions..) and its associated global addresses, along with some other
>usefull stuff, like a CRC value, and the module exporting every specific
>symbol.
>Fine until this point.
>
>In 2.6 kernels, /proc/ksyms disappeared. Many sources suggest that it
>was replaced by the /proc/kallsyms file.
>BUT this file seems to be something completely different, and I haven't
>figured out in what way it is different. It seems that it's not the
>kernels public symbols table.
>
>So, some questions to anyone that knows more on this:
>
>1. Is my description of the functionality of /proc/ksyms in 2.4 kernels
>correct?

Yes.

>2. What exactly the /proc/kallsyms file contains? Why does this file
>exist and how is it used?

kallsyms contains (as the name suggests) all the global symbols in the
kernel and the loaded modules.  It was originally added for kernel
debugging but it became so useful that it supplanted ksyms.

>4. If one wants to find out what are the exported symbols from some
>module, so to know which symbols can he use in a future module, how can
>he achieve this?

nm <path_to_module.ko> | grep __ksymtab


      parent reply	other threads:[~2008-11-10  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  1:00 /proc/ksyms and /proc/kallsyms relationship? John K
2008-11-10  3:37 ` Arjan van de Ven
2008-11-10 13:02 ` Keith Owens [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=18101.1226322131@ocs10w \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trv@freemail.gr \
    /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