[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTi=JXq+V783amiJB-qLX=7PaeH-83w@mail.gmail.com>
Date: Wed, 11 May 2011 10:47:19 -0400
From: Mike Frysinger <vapier.adi@...il.com>
To: Alessio Igor Bogani <abogani@...nel.org>
Cc: Rusty Russell <rusty@...tcorp.com.au>,
Tim Abbott <tabbott@...lice.com>,
Anders Kaseorg <andersk@...lice.com>,
Jason Wessel <jason.wessel@...driver.com>,
Tim Bird <tim.bird@...sony.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux Embedded <linux-embedded@...r.kernel.org>
Subject: Re: [PATCH 0/4] Speed up the symbols' resolution process V4
On Wed, May 11, 2011 at 05:19, Alessio Igor Bogani wrote:
>> name. so rather than "__", use "+".
>
> Sorry I don't think that is a good choice from a long term point of
> view. What do you think to add MODULE_SYMBOL_PREFIX to section names
> instead? In this way symbol and section names should always be
> different also on symbol prefixed archs (which are blackfin and
> h8300).
that doesnt work. it simply delays the problem to another set of
underscores. so with that change, local_bh_enable/_local_bh_enable
work, but now send_remote_softirq/__send_remote_softirq fail:
CC kernel/softirq.o
nano /tmp/cconhYy1.s: Assembler messages:
/tmp/cconhYy1.s:3664: Error: symbol `___ksymtab___send_remote_softirq'
is already defined
make[1]: *** [kernel/softirq.o] Error 1
so any option that involves using underscores as the separator will
not work. pick something else, like "+" or "." or ... i dont see a
problem with using these.
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists