All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Xenomai LTTng support
Date: Wed, 25 Mar 2009 12:17:51 +0100	[thread overview]
Message-ID: <1237979871.6815.69.camel@domain.hid> (raw)
In-Reply-To: <49C95A76.4020802@domain.hid>

On Tue, 2009-03-24 at 23:11 +0100, Jan Kiszka wrote:
> vikesh rambaran wrote:
> >>
> >> That's the only advantage of svn over git: If you do not know a precise
> >> command for the moment, you can guess it and it will probably be right.
> >> Don't try this with git (like I did)... :)
> > 
> > 
> > Agreed, that's why i also keep the user manuals close by !
> > 
> >>>>> 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).
> >>> Ok , will do so and post the updated diff
> >> Looking forward!
> >>
> > 
> > Attached is the patch created using diff. Please check and confirm if it's
> > what you had in mind.
> > Besides the trace_mark calls in the functions, a minor mod was also required
> > for the trace_mark in
> > MAJOR_FUNCTION_WRAPPER_TH
> 
> Looks consistent. Maybe we can merge it into the stable series.
> Philippe, what do you think?
> 

Looks good and does not break any user-level interface, so this should
be fine for 2.4.x as well.

> > 
> > Would have liked to create the diff using the git format that seems to
> > xenomai's standard. However, the cloned
> > git repository from git://git.kiszka.org/xenomai.git did not have a 2.4.7
> > tag, so i used the released 2.4.7 tar.bz2
> > as the reference.
> > 
> 
> Thanks, fixed. My update script was lacking some magic git svn parameter.
> 
> > 
> > Regarding building of the kernel, LTT function tracer gives a problem if
> > enabled. Build stops with the following error
> > 
> > "  CC      kernel/bounds.s
> > gcc: -pg and -fomit-frame-pointer are incompatible "
> > 
> > I deselected the feature for now.
> 
> Could you provide the corresponding .config that triggered this?
> 
> > 
> > 
> > Besides that, the kernel does boot although X + keyboard + mouse seems to
> > lock up occasionally.
> 
> Is the lockup permanent then, or does the system recover from it later?
> 
> > It does not seem to be LTTng specific, as i've noticed it with a xenomai
> > enabled kernel only as well. Will try
> > isolating the problem with a vanilla kernel soon.
> > 
> > For reference, the other LTT tools used are
> > LTT control  : ltt-control-0.62-23122008
> > LTTV          : lttv-0.12.9-29012009
> > 
> > Both obtained from  http://ltt.polymtl.ca/
> > 
> > The good news is that with the above combination, i did manage to capture a
> > trace with a xenomai application
> > running and view the information using lttv. Understanding what's happening
> > there is another story - feels like
> > information OVERLOAD :)
> 
> That's kind of normal. Maybe you want to start with looking at the
> xn_nucleus.sched_switch events - the Xenomai task switches. Hope we have
> a plugin for some LTT viewer for Xenomai tracepoints one day - but my
> current feeling that it's better to wait for the LTTV "rewrite" as
> Eclipse plugin that is promised for this year.
> 
> > 
> > Will have to spend some time getting used to the environment and features
> > before posting any more questions ...
> > 
> > 
> > Thanx for all the help
> > Vicki
> > 
> 
> Jan
> 
-- 
Philippe.




  reply	other threads:[~2009-03-25 11:17 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
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 [this message]
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=1237979871.6815.69.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@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.