From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49C95A76.4020802@domain.hid> Date: Tue, 24 Mar 2009 23:11:02 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <49C7899F.5030306@domain.hid> <49C91B24.2020304@domain.hid> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDAD676DF6C43444BB8F5EFD0" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-help] Xenomai LTTng support List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: vikesh rambaran Cc: xenomai-help This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDAD676DF6C43444BB8F5EFD0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable vikesh rambaran wrote: >> >> That's the only advantage of svn over git: If you do not know a precis= e >> command for the moment, you can guess it and it will probably be right= =2E >> Don't try this with git (like I did)... :) >=20 >=20 > Agreed, that's why i also keep the user manuals close by ! >=20 >>>>> c) Applying the xenomai instrumentation patch from >>>>> [http://permalink.gmane.org/gmane.linux.real-time.xenomai.devel/600= 9] >>>> 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 fro= m >>>> that patch). >>> Ok , will do so and post the updated diff >> Looking forward! >> >=20 > Attached is the patch created using diff. Please check and confirm if i= t's > what you had in mind. > Besides the trace_mark calls in the functions, a minor mod was also req= uired > 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? >=20 > 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= =2E7 > tag, so i used the released 2.4.7 tar.bz2 > as the reference. >=20 Thanks, fixed. My update script was lacking some magic git svn parameter.= >=20 > Regarding building of the kernel, LTT function tracer gives a problem i= f > enabled. Build stops with the following error >=20 > " CC kernel/bounds.s > gcc: -pg and -fomit-frame-pointer are incompatible " >=20 > I deselected the feature for now. Could you provide the corresponding .config that triggered this? >=20 >=20 > 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 xenoma= i > enabled kernel only as well. Will try > isolating the problem with a vanilla kernel soon. >=20 > For reference, the other LTT tools used are > LTT control : ltt-control-0.62-23122008 > LTTV : lttv-0.12.9-29012009 >=20 > Both obtained from http://ltt.polymtl.ca/ >=20 > The good news is that with the above combination, i did manage to captu= re a > trace with a xenomai application > running and view the information using lttv. Understanding what's happe= ning > 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. >=20 > Will have to spend some time getting used to the environment and featur= es > before posting any more questions ... >=20 >=20 > Thanx for all the help > Vicki >=20 Jan --------------enigDAD676DF6C43444BB8F5EFD0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknJWnsACgkQniDOoMHTA+kawwCfQOE0T4JI592bYSvW2prMwTAx ZW0AnRcLy0vxKjtcD9ArXK5DJFatqekq =LRCG -----END PGP SIGNATURE----- --------------enigDAD676DF6C43444BB8F5EFD0--