From: Philippe Gerum <rpm@xenomai.org>
To: Anders Blomdell <anders.blomdell@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] __raw_*lock for Xenaomai 2.01 on ppc
Date: Tue, 22 Nov 2005 19:53:54 +0100 [thread overview]
Message-ID: <43836942.2020901@domain.hid> (raw)
In-Reply-To: <4382CEF6.7020109@domain.hid>
Anders Blomdell wrote:
>>> Is it by design or mistake that I get the following undefined symbols
>>> on a PowerPC
>>>
>>> # insmod xeno_nucleus.ko
>>> xeno_nucleus: Unknown symbol __raw_read_lock
>>> xeno_nucleus: Unknown symbol __raw_write_unlock
>>> xeno_nucleus: Unknown symbol __raw_read_unlock
>>> xeno_nucleus: Unknown symbol __raw_write_lock
>>>
>>> unless the kernel is compiled with:
>>>
>>> CONFIG_DEBUG_KERNEL=y
>>> CONFIG_DEBUG_SPINLOCK=y
>>
>> Patch version, please.
>
> xenomai-2.0.1/arch/ppc/patches/adeos-ipipe-2.6.14-ppc-1.0-06.patch
>
> The problem probably is that the EXPORT_SYMBOL are done in
> lib/spinlock_debug.c, which is only compiled if CONFIG_DEBUG_SPINLOCK=y
>
lib/debug_spinlock.c adds exports for the _raw_* symbols, not for
__raw_* ones (actually, I did add those since they were missing in the
vanilla kernel in the first place). At first sight, the issue looks like
related to linux/spinlock_up.h not defining no-ops for those symbols in
the non-debug case. Maybe another vanilla kernel issue.
--
Philippe.
prev parent reply other threads:[~2005-11-22 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 16:56 [Xenomai-help] __raw_*lock for Xenaomai 2.01 on ppc Anders Blomdell
2005-11-21 18:29 ` Philippe Gerum
2005-11-22 7:55 ` Anders Blomdell
2005-11-22 18:53 ` Philippe Gerum [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=43836942.2020901@domain.hid \
--to=rpm@xenomai.org \
--cc=anders.blomdell@domain.hid \
--cc=xenomai@xenomai.org \
/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.