From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Steven Scholz <steven.scholz@domain.hid>
Cc: Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] latency hangs on AT91RM9200
Date: Fri, 23 Feb 2007 16:05:20 +0100 [thread overview]
Message-ID: <45DF02B0.4090406@domain.hid> (raw)
In-Reply-To: <45DEFB2F.10103@domain.hid>
Steven Scholz wrote:
> Hi,
>
>
>>>schedule. Anyway, I think the tracer will give better results than a
>>>simple backtrace.
>>
>>Ok. Thanks.
>>
>>So what exactly shell I do? I have never worked with "the tracer".
>
>
> Just enabled
>
> CONFIG_IPIPE_DEBUG=y
> CONFIG_IPIPE_TRACE=y
> CONFIG_IPIPE_TRACE_ENABLE=y
> CONFIG_IPIPE_TRACE_MCOUNT=y
> CONFIG_IPIPE_TRACE_IRQSOFF=y
> CONFIG_IPIPE_TRACE_SHIFT=15
> # CONFIG_IPIPE_TRACE_VMALLOC is not set
> CONFIG_IPIPE_TRACE_ENABLE_VALUE=1
>
> but get
>
> CC arch/arm/kernel/asm-offsets.s
> In file included from include/linux/bitops.h:9,
> from include/linux/thread_info.h:20,
> from include/linux/preempt.h:9,
> from include/linux/spinlock.h:49,
> from include/linux/capability.h:45,
> from include/linux/sched.h:46,
> from arch/arm/kernel/asm-offsets.c:13:
> include/asm/bitops.h: In function `____atomic_set_bit':
> include/asm/bitops.h:40: warning: implicit declaration of function `local_test_iflag_hw'
At first sight, replacing local_test_iflag_hw with
raw_irqs_disabled_flags should work.
--
Gilles Chanteperdrix
next prev parent reply other threads:[~2007-02-23 15:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 11:27 [Xenomai-core] latency hangs on AT91RM9200 Steven Scholz
2007-02-23 13:16 ` Gilles Chanteperdrix
2007-02-23 13:26 ` Philippe Gerum
2007-02-23 13:53 ` Steven Scholz
2007-02-23 13:50 ` Steven Scholz
2007-02-23 13:57 ` Philippe Gerum
2007-02-23 13:56 ` Steven Scholz
2007-02-23 14:12 ` Philippe Gerum
2007-02-23 14:16 ` Steven Scholz
2007-02-23 14:11 ` Gilles Chanteperdrix
2007-02-23 14:14 ` Steven Scholz
2007-02-23 14:21 ` Jan Kiszka
2007-02-23 15:02 ` Steven Scholz
2007-02-23 15:09 ` Jan Kiszka
2007-02-23 14:24 ` Gilles Chanteperdrix
2007-02-23 14:33 ` Steven Scholz
2007-02-23 15:05 ` Gilles Chanteperdrix [this message]
2007-02-23 14:36 ` Jan Kiszka
2007-02-23 14:39 ` Steven Scholz
2007-02-23 14:41 ` Jan Kiszka
2007-02-26 10:11 ` Steven Scholz
2007-02-23 13:25 ` Philippe Gerum
2007-02-23 13:49 ` Steven Scholz
2007-02-23 15:14 ` Steven Scholz
2007-02-23 15:23 ` Gilles Chanteperdrix
2007-02-23 15:28 ` Jan Kiszka
2007-02-23 16:41 ` Gilles Chanteperdrix
2007-02-26 10:17 ` Gilles Chanteperdrix
2007-02-26 11:21 ` Gilles Chanteperdrix
2007-02-26 13:36 ` Steven Scholz
2007-03-08 8:28 ` Steven Scholz
2007-03-08 8:43 ` Gilles Chanteperdrix
2007-03-08 8:46 ` Steven Scholz
2007-03-08 9:18 ` Gilles Chanteperdrix
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=45DF02B0.4090406@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai-core@domain.hid \
--cc=steven.scholz@domain.hid \
/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.