From: Jan Kiszka <jan.kiszka@domain.hid>
To: Jean-Michel Hautbois <jhautbois@domain.hid>
Cc: Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] P2020 support for ftrace with ipipe 2.12-01 and xeno 2.5.5.1
Date: Fri, 23 Sep 2011 16:10:22 +0200 [thread overview]
Message-ID: <4E7C934E.5090900@domain.hid> (raw)
In-Reply-To: <CAL8zT=gbd9tdUvBirZYxrqVeHxdVjny6TLWo8diQs6Ay0ZA-nw@domain.hid>
On 2011-09-23 15:58, Jean-Michel Hautbois wrote:
> 2011/9/23 Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
>
>> On 09/23/2011 11:49 AM, Jean-Michel Hautbois wrote:
>>> OK, I have more traces (a few :)) :
>>
>> I meant the I-pipe tracer alone. The I-pipe tracer intead of other
>> ftrace tracers.
>>
>>
> Well, I think it works, I can do a cat /proc/ipipe/trace/max without any
> error in a kernel which doesn't have any other ftrace function.
> Do you have one test in particular in mind ?
Check
http://git.kiszka.org/?p=ipipe.git;a=shortlog;h=refs/heads/queues/2.6.35-x86-trace
to get an impression of what is required to get ftrace working on
x86_64. It is not working on x86_32 e.g. as it depends on the arch
providing a NMI-safe, ie. task-stack independent current_thread_info().
That is also not yet the case on Power.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-09-23 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 7:58 [Xenomai-core] P2020 support for ftrace with ipipe 2.12-01 and xeno 2.5.5.1 Jean-Michel Hautbois
2011-09-23 8:43 ` Gilles Chanteperdrix
2011-09-23 9:21 ` Jean-Michel Hautbois
2011-09-23 9:49 ` Jean-Michel Hautbois
2011-09-23 11:02 ` Gilles Chanteperdrix
2011-09-23 13:58 ` Jean-Michel Hautbois
2011-09-23 14:10 ` Jan Kiszka [this message]
2011-09-23 14:21 ` Jean-Michel Hautbois
2011-09-23 14:29 ` Jan Kiszka
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=4E7C934E.5090900@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Xenomai-core@domain.hid \
--cc=jhautbois@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.