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: Sun, 04 Sep 2011 15:52:30 +0200 [thread overview]
Message-ID: <4E63829E.1090500@domain.hid> (raw)
In-Reply-To: <CAG0ejMFKjFdvhXWLabv5+V8sJy=OXdpP=XZAUasHS2PEGqTg8g@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On 2011-09-04 15:16, rainbow wrote:
> 2011/9/4 Jan Kiszka <jan.kiszka@domain.hid>
>
>> On 2011-09-04 14:21, rainbow wrote:
>>> Is the ipipe patch the same as patch like
>>> adeos-ipipe-2.6.37.6-x86-2.9-02.patch,
>>
>> Except that the trace branch is for 2.6.35, yes. More precisely it is
>> now the same, I just pushed the latest version that includes two more
>> backported ipipe fixes.
>>
>>> I know the latter is xenomai patch
>>> and after I patch it, I can see "Real-time sub-system ---> " Option. But
>> If
>>> I use 2.6.35-x86-trace which contains ,there is no such option.
>>
>> That menu option is introduced by Xenomai, ie. after running
>> prepare-kernel.sh. You likely forgot that step.
>>
>
>
>> Yes,I forget the step. So I think I only have to run prepare-kernel.sh
>> --arch=x86_64
>
> --linux=2.6.35-x86-trace , I do not need --adeos option because
>> the 2.6.35-x86-trace contains the ipipe patch.
>>
>
>
>
>> Note again that you have to use a Xenomai tree with the required ftrace
>> patches on top if you want Xenomai to generate ftrace events as well.
>>
>> "Xenomai tree with required ftrace patches on top" you mean the branch
> "remotes/origin/queues/ftrace"?
Yep. I just pushed a rebased version of current git master.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-09-04 13:52 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 [this message]
2011-09-04 14:12 ` rainbow
2011-09-05 2:32 ` rainbow
2011-09-05 6:53 ` Jan Kiszka
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=4E63829E.1090500@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.