From: Wolfgang Grandegger <wg@grandegger.com>
To: dietmar.schindler@manroland.com
Cc: Xenomai@xenomai.org
Subject: Re: [Xenomai] ftrace
Date: Wed, 13 Jun 2012 11:49:35 +0200 [thread overview]
Message-ID: <4FD8622F.2050006@grandegger.com> (raw)
In-Reply-To: <8236197CA3DA864F9EF20609D9887263B7F88212@rrxchngmbx01.mro.roland-man.biz>
Hi Dietmar,
On 06/13/2012 11:32 AM, dietmar.schindler@manroland.com wrote:
>> From: Philippe Gerum [mailto:rpm@xenomai.org]
>> Sent: Tuesday, June 05, 2012 10:17 AM
>>
>> On 06/05/2012 10:06 AM, dietmar.schindler@manroland.com wrote:
>>> A Xenomai-patched 2.6.34 kernel (ppc GNU/Linux) crashes when issuing the
>> command
>>>
>>> echo function>/sys/kernel/debug/tracing/current_tracer
>>>
>>> (sometimes displaying NIP in a function from
>> "source/kernel/trace/ring_buffer.c", sometimes with no message).
>>>
>>> Are Xenomai and ftrace incompatible?
>>>
>>
>> No, but some ftrace bits have to be made pipeline-aware. The generic
>> ones should be, but some powerpc-specific fix ups might be missing. I'm
>> not using/testing ftrace routinely when upgrading patches. Also, 2.6.34
>> is fairly old.
>
> http://www.xenomai.org/index.php/I-pipe:Tracer#Configuration says: "Ftrace's function and graph tracers themselves are still not usable over I-pipe kernels, latest I-pipe will prevent conflicting use."
>
> I'm confused - I can't gather from this whether the Function Tracer might work or can't possibly work.
If the iPipe-Tracer is enabled in the Kernel, you can't use Linux ftrace
via "/sys/kernel/debug/tracing" any more. I checked that for PowerPC up
to Linux 3.2.1. In contrast, the iPipe-Tracer is controlled by files in
/proc/ipipe/trace and that works. For your kernel version you need the
attached two patches, though.
Wolfgang.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: adeos-ipipe-2.6.34.4-powerpc-2.10-05-tracer.patch
Type: text/x-diff
Size: 592 bytes
Desc: not available
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20120613/c8f10542/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: adeos-ipipe-2.6.34.4-powerpc-2.10-05-tsc2us.patch
Type: text/x-diff
Size: 1279 bytes
Desc: not available
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20120613/c8f10542/attachment-0001.patch>
next prev parent reply other threads:[~2012-06-13 9:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 14:35 [Xenomai] a question about ADEOS ali hagigat
2012-05-30 14:57 ` Chris Stone
2012-05-30 15:08 ` Philippe Gerum
2012-05-30 15:27 ` Gilles Chanteperdrix
2012-05-30 15:57 ` Lennart Sorensen
2012-05-30 16:53 ` Gilles Chanteperdrix
2012-05-30 17:57 ` Lennart Sorensen
2012-05-30 18:40 ` Gilles Chanteperdrix
2012-05-30 17:32 ` Chris Stone
2012-05-30 17:59 ` Lennart Sorensen
2012-05-30 21:40 ` Gilles Chanteperdrix
2012-05-31 15:10 ` Chris Stone
2012-06-05 6:26 ` ali hagigat
2012-06-05 7:10 ` Philippe Gerum
2012-06-05 8:06 ` [Xenomai] ftrace dietmar.schindler
2012-06-05 8:17 ` Philippe Gerum
2012-06-13 9:32 ` dietmar.schindler
2012-06-13 9:49 ` Wolfgang Grandegger [this message]
2012-06-13 10:00 ` Wolfgang Grandegger
2012-06-05 7:20 ` [Xenomai] a question about ADEOS Philippe Gerum
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=4FD8622F.2050006@grandegger.com \
--to=wg@grandegger.com \
--cc=Xenomai@xenomai.org \
--cc=dietmar.schindler@manroland.com \
/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.