From: Jan Kiszka <jan.kiszka@domain.hid>
To: rainbow <lvqq05@domain.hid>
Cc: Xenomai-core@domain.hid
Subject: Re: [Xenomai-core] xenomai-core ftrace
Date: Mon, 05 Sep 2011 08:53:28 +0200 [thread overview]
Message-ID: <4E6471E8.90001@domain.hid> (raw)
In-Reply-To: <CAG0ejMEyzyvr79Bf8x79R65+u3MBapCPq3t_RGarfDGaLVe+Zg@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
On 2011-09-05 04:32, rainbow wrote:
> hi,
> I did a test for ftrace-xenomai on x86_64 test just now:
> the environment is : OS: debian 6.0 gcc-4.1
> I use origin/queues/2.6.37-x86 branch on git
> git://git.kiszka.org/ipipe-2.6for linux kernel and use branch
> origin/queues/ftrace on git git://
> git.xenomai.org/xenomai-jki.git
> then I do as the following procedures:
> 1,cd xenomai git
> 2, ./scripts/prepare-kernel.sh --arch=x86_64 --linux=path_to_2.6.37-x86
> 3, cd path_to_2.6.37_x86
> 4,make menuconfig
> then enble ftrace on kernel hacking option.
> 5,install the kernel and reboot the machine.
> 6,do ftrace test
> 6.1 mount -t debugfs nodev /sys/kernel/debug
> 6.2 cd /sys/kernel/debug/tracing
> 6.3 echo function > current_tracer
> At last the machine reboot.
> Is there something wrong about the above procedure? Thanks!
Only queues/2.6.35-x86-trace contains ftrace support.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-09-05 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 2:52 [Xenomai-core] xenomai-core ftrace rainbow
2011-09-03 6:58 ` Jan Kiszka
2011-09-04 5:10 ` rainbow
2011-09-04 11:24 ` Jan Kiszka
2011-09-04 11:49 ` rainbow
2011-09-04 11:52 ` Jan Kiszka
2011-09-04 12:21 ` rainbow
2011-09-04 12:34 ` Jan Kiszka
2011-09-04 13:16 ` rainbow
2011-09-04 13:52 ` Jan Kiszka
2011-09-04 14:12 ` rainbow
2011-09-05 2:32 ` rainbow
2011-09-05 6:53 ` Jan Kiszka [this message]
2011-09-05 7:39 ` rainbow
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=4E6471E8.90001@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Xenomai-core@domain.hid \
--cc=lvqq05@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.