public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* logging in kernel
@ 2004-03-26 22:24 khandelw
  2004-03-27  5:53 ` Karim Yaghmour
  0 siblings, 1 reply; 2+ messages in thread
From: khandelw @ 2004-03-26 22:24 UTC (permalink / raw)
  To: linux-kernel

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.


I am not sure whether such a tool is required but I believe it will give me a
taste of kernel programming.

Any suggestions would be highly appreciated.

Thanking you all in anticipation.
-- Amit Khandelwal





^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: logging in kernel
  2004-03-26 22:24 logging in kernel khandelw
@ 2004-03-27  5:53 ` Karim Yaghmour
  0 siblings, 0 replies; 2+ messages in thread
From: Karim Yaghmour @ 2004-03-27  5:53 UTC (permalink / raw)
  To: khandelw; +Cc: linux-kernel


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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-27  5:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-26 22:24 logging in kernel khandelw
2004-03-27  5:53 ` Karim Yaghmour

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox