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: Sat, 3 Apr 2004 18:42:48 -0500 [thread overview]
Message-ID: <005901c419d5$5ecd7c70$af7aa8c0@VALUED65BAD02C> (raw)
In-Reply-To: <406F476D.8050002@opersys.com>
Hey Karim,
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.
Thanks!
-Amit Khandelwal
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.
----- 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 6:23 PM
Subject: Re: kernel 2.4.16
>
> Amit wrote:
> > The patches got installed smoothly however, like in linux-2.4.19 this
> > time the "Kernel Tracing" option didn't come up when I did "make
xconfig". I
> > copied the CONFIG_TRACE=m from my .config of linux-2.4.19. I hope this
is
> > correct.
>
> No, this isn't the right way.
>
> You need to enable relayfs support in "File Systems"->"Pseudo
filesystems",
> then you will be able to select "General setup"->"Linux Trace Toolkit
support".
>
> 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
>
next prev parent reply other threads:[~2004-04-03 23:42 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 [this message]
2004-04-03 23:59 ` Karim Yaghmour
2004-04-04 14:42 ` Amit
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='005901c419d5$5ecd7c70$af7aa8c0@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®