linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Keith Owens <kaos@melbourne.sgi.com>
To: Thomas Graichen <graichen@innominate.de>, thomas.graichen@innominate.de
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: SGI XFS on ppc
Date: Mon, 31 Jul 2000 16:34:17 +1000	[thread overview]
Message-ID: <15081.965025257@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "31 Jul 2000 06:12:29 GMT." <news2mail-8m35cd$3nu$2@mate.bln.innominate.de>


On 31 Jul 2000 06:12:29 GMT,
Thomas Graichen <news-innominate.list.sgi.xfs@innominate.de> wrote:
>Keith Owens <kaos@ocs.com.au> wrote:
>> More specific please.  kallsyms has no ifdefs.  It should only be
>> included if you select kdb but kdb has not been ported to ppc.  I
>> maintain modutils, kallsyms and kdb.
>
>just have a look at the diff at
>
>  http://innominate.org/~graichen/projects/xfs-ppc/

I can see the problem but need some ppc help in fixing it.  Part of the
kallsyms patch updates arch/xxx/vmlinux.lds on every arch.  I did not
patch arch/ppc/vmlinux.lds because it did not have any entries for
section __ksymtab.  kallsyms is module related and the absence of
__ksymtab in arch/ppc/vmlinux.lds made me think that ppc does not use
modules.

Does ppc support modules?  I know that modutils has an obj-ppc.c file
but I don't think I have ever seen any ppc bug reports for modutils.
If ppc does use modutils then we need lines like this in
arch/ppc/vmlinux.lds.

  __start___ksymtab = .;        /* Kernel symbol table */
  __ksymtab : { *(__ksymtab) }
  __stop___ksymtab = .;

  __start___kallsyms = .;       /* All kernel symbols */
  __kallsyms : { *(__kallsyms) }
  __stop___kallsyms = .;

The first section is standard for any arch that supports modules but is
not in pppc for some reason.  The second section is part of kallsyms.
Most of the kallsyms code needs to be wrapped in #ifdef but
arch/xxx/vmlinux.lds, include/modules.h and kernel/module.c do not,
they are global to provide a standard userspace ABI, independent of
kernel options.

If ppc does not support modules then forget the above update.  However
the code in kernel/module.c that refers to kallsyms entries should not
be compiled when CONFIG_MODULES=n is set, why is it being compiled?


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2000-07-31  6:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <news2mail-8m35cd$3nu$2@mate.bln.innominate.de>
2000-07-31  6:34 ` Keith Owens [this message]
2000-07-31  6:48   ` SGI XFS on ppc Thomas Graichen
2000-07-31  8:02   ` Michel Dänzer
2000-07-31  6:17 Thomas Graichen
  -- strict thread matches above, loose matches on Subject: below --
2000-07-31  0:33 Thomas Graichen
2000-07-31  0:51 ` Keith Owens
2000-07-31  1:20   ` Dan Malek
2000-07-31  2:02     ` Keith Owens
2000-07-31  2:10       ` Dan Malek
2000-07-31 11:59 ` Geert Uytterhoeven
2000-07-31 16:29   ` Steve Lord

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=15081.965025257@ocs3.ocs-net \
    --to=kaos@melbourne.sgi.com \
    --cc=graichen@innominate.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=thomas.graichen@innominate.de \
    /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;
as well as URLs for NNTP newsgroup(s).