From: Karim Yaghmour <karim@opersys.com>
To: khandelw@cs.fsu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: logging in kernel
Date: Sat, 27 Mar 2004 00:53:11 -0500 [thread overview]
Message-ID: <406516C7.40705@opersys.com> (raw)
In-Reply-To: <1080339875.8f2cd36818efd@system.cs.fsu.edu>
khandelw@cs.fsu.edu wrote:
> Hello,
> I am a graudate student at Florida State University. My friends and my self
> are planning to implement a kernel logger for linux kernel (real-time systems).
> We are new to linux kernel programming and we have not done kernel programming.
> We believe right now most of the system are using printk. We want to write a
> tool which can be used for debugging as well as logging of data in the future.
> Following are the things that we have in mind so far.
>
> 1. Implement the logging daemon or the server as a periodic task in the
> real-time system.
> 2. Have an api which looks similar to printk
> 3. Have an option to specify the write the network card or console or a
> dedicated device.
> 4. Use it for checkpointing in distributed system.
There have been quite a few things done in this area already. For starters,
you may want to take a look at the Linux Trace Toolkit and the underlying
mechanism, relayfs:
http://www.opersys.com/ltt/index.html
http://www.opersys.com/relayfs/index.html
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
prev parent reply other threads:[~2004-03-27 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 22:24 logging in kernel khandelw
2004-03-27 5:53 ` Karim Yaghmour [this message]
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=406516C7.40705@opersys.com \
--to=karim@opersys.com \
--cc=khandelw@cs.fsu.edu \
--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 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.