mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Amit" <khandelw@cs.fsu.edu>
To: <karim@opersys.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.4.16
Date: Sun, 4 Apr 2004 10:42:47 -0400	[thread overview]
Message-ID: <006101c41a53$1913eb00$b07aa8c0@VALUED65BAD02C> (raw)
In-Reply-To: <406F4FCD.7020506@opersys.com>

Hello Karim,
    We have got LTT running for 2.6.3 and 2.419. We collected some traces
for both 2.4.19 and 2.6.3. The gui looks really cool. However, just one
thing with 2.6.3 when I feed in the trace file and the proc file it dumps
core.

I execute the following command :-
- tracedaemon -ts10 ./out.trace ./out.proc
to get the trace and the proc file.

Thanks,
Amit Khandelwal





----- Original Message ----- 
From: "Karim Yaghmour" <karim@opersys.com>
To: "Amit" <khandelw@cs.fsu.edu>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Sent: Saturday, April 03, 2004 7:59 PM
Subject: Re: kernel 2.4.16


>
> Amit wrote:
> >    The installation has gone through smoothly and I have managed to get
an
> > linux-2.6.3 up and running with LTT.
> > I checked the documentation and it says that I need to do an insmod on
the
> > tracer but I have compiled it as a part of the kernel. Now the
documentation
> > says that I should execute the createdev.sh to create the devices. When
I
> > execute that I get errors related to tracer. When I try to execute the
> > tracedaemon I get that relayfs is not mounted. Can you please tell me
how to
> > go about doing the first part. After doing all this I want to run some
test
> > cases and see how does LTT generate traces. Later on I would also like
to
> > add rtai to this and see the traces from that too.
>
> The documentation is out of date. Basically, the createdev.sh script isn't
> needed anymore because of relayfs. You need to mount relayfs to use LTT.
> See the classic dox on filesystem mounting for this kind of thing. It's
> going to be something like:
> # mount -t relayfs nodev /mnt/relay
>
> There's no insmod for LTT. It isn't a device driver module, following LKML
> recommendations.
>
> As for RTAI, there's currently no RTAI support in relayfs. If you want to
have
> RTAI tracing, then you'd have to fall back on earlier stable versions of
LTT.
>
> > PS. I would like to write down a small howto on this and pass it on to
you
> > so that newbies like me can have a good ref. Thanks for the help.
>
> Sure.
>
> Karim
> -- 
> Author, Speaker, Developer, Consultant
> Pushing Embedded and Real-Time Linux Systems Beyond the Limits
> http://www.opersys.com || karim@opersys.com || 1-866-677-4546
>



  reply	other threads:[~2004-04-04 14:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 20:03 khandelw
2004-04-01 20:21 ` Karim Yaghmour
2004-04-01 20:31   ` Karim Yaghmour
2004-04-03 17:13   ` khandelw
2004-04-03 20:42     ` Karim Yaghmour
2004-04-03 21:00       ` khandelw
2004-04-03 21:10         ` Karim Yaghmour
2004-04-03 23:07           ` Amit
2004-04-03 23:23             ` Karim Yaghmour
2004-04-03 23:42               ` Amit
2004-04-03 23:59                 ` Karim Yaghmour
2004-04-04 14:42                   ` Amit [this message]
2004-04-05 20:04                     ` Karim Yaghmour

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='006101c41a53$1913eb00$b07aa8c0@VALUED65BAD02C' \
    --to=khandelw@cs.fsu.edu \
    --cc=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®