From: Jan Kiszka <jan.kiszka@domain.hid>
To: vikesh rambaran <vikesh.rambaran@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Xenomai LTTng support
Date: Mon, 23 Mar 2009 14:07:43 +0100 [thread overview]
Message-ID: <49C7899F.5030306@domain.hid> (raw)
In-Reply-To: <b131c9f0903230100x1b2aa2fet9e2b0efe68a7a77f@domain.hid>
vikesh rambaran wrote:
> Hi
>
> I'm trying to get LTTng support for Xenomai 2.4.7 with Linux 2.6.28.7
> running.
> With regards the mailing list, the latest one seems to be
>
> [ date Tue, Feb 24, 2009 at 8:30 PM
> subject [Xenomai-help] [ANNOUNCE] LTTng-over-I-pipe git tree
> ]
>
> My understanding of the sequence is :
> (please correct as necessary)
>
> 1. Get the tree which already has LTTng and ipipe patched in
> 2. Apply trace_mark channel event patch to xenomai 2.4.7
> 3. Apply xenomai patches to kernel
> 4. Build and install
>
> However, I am having trouble with the following and would appreciate help
>
> a) "git clone git://git.kiszka.org/ipipe-2.6.git lttng/2.6.28-x86"
> as per the email, results in the 2.6.29-rc6. What should the command be
> to access the 2.6.28 tree ?
Additionally try "git checkout lttng/2.6.28-x86".
>
> Note : downloading ipipe-2.6.28.7-x86-2.2-06 from
> http://git.kiszka.org/?p=ipipe-2.6.git;a=commit;h=7abbb32f691345126d96cb6b48c587e145b8ef20
> using the web interface gives the 2.6.28.7 tree. Is this ok to use ?
>
> b) The LTTng manual mentions that there should be a kernel option
> Linux Trace Toolkit Next Generation (LTTng) under General settings. This
> seems to be
> unavailable for both the above trees. What must be done to enable this
> feature ?
It will be available in the git branch that contains LTTng.
>
> c) Applying the xenomai instrumentation patch from
> [http://permalink.gmane.org/gmane.linux.real-time.xenomai.devel/6009] to
> the xenomai 2.4.7
> tree using patch -p1 < "filename", results in numerous hunks. What am i
> doing wrong ?
Hmm, I'm afraid the patch has to be back-ported manually. It was
developed against the instrumentation points in trunk, 2.4.x looks a bit
different (but you should be able to derive the adoption pattern from
that patch).
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-03-23 13:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 8:00 [Xenomai-help] Xenomai LTTng support vikesh rambaran
2009-03-23 13:07 ` Jan Kiszka [this message]
2009-03-24 7:37 ` vikesh rambaran
2009-03-24 17:40 ` Jan Kiszka
2009-03-24 21:37 ` vikesh rambaran
2009-03-24 22:11 ` Jan Kiszka
2009-03-25 11:17 ` Philippe Gerum
2009-03-25 13:36 ` vikesh rambaran
2009-04-06 8:26 ` vikesh rambaran
2009-04-06 10:57 ` Jan Kiszka
2009-04-07 10:19 ` Vikesh Rambaran
2009-04-07 11:20 ` Jan Kiszka
2009-04-08 7:57 ` vikesh rambaran
2009-04-08 8:53 ` Jan Kiszka
2009-04-14 8:12 ` Vikesh Rambaran
2009-04-14 9:16 ` Jan Kiszka
2009-04-14 11:26 ` Vikesh Rambaran
2009-04-14 11:35 ` Jan Kiszka
[not found] ` <1239709765.5780.40.camel@domain.hid>
[not found] ` <49E4793D.2010105@domain.hid>
2009-04-14 13:55 ` Vikesh Rambaran
2009-04-14 14:13 ` Jan Kiszka
2009-04-17 15:44 ` vikesh rambaran
2009-04-18 10:27 ` Philippe Gerum
2009-04-19 18:23 ` vikesh rambaran
2009-03-23 13:12 ` Andreas Glatz
2009-03-23 13:17 ` Andreas Glatz
2009-03-23 13:40 ` 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=49C7899F.5030306@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=vikesh.rambaran@domain.hid \
--cc=xenomai@xenomai.org \
/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.