losing interrupts - printk is bad

[Mike Neuhauser]

In message <3AB63E12.6D38973E at esd-electronics.com>, Matthias Fuchs writes:

  [stuff about losing interrupts during printk to serial console deleted]

> Second, could anybody explain t ome, what klogd is doing ? It would be
> glad to get klogd read all the debugging output from the kernel and
> output the data from user space (well buffered and not blocking the
> whole system). It seems that klogd cannot do that, am I right ?

klogd reads the kernel log messages (i.e. printk messages) either via syscall
or /proc interface and hands them over to syslogd.

Syslogd in turn writes them to a terminal, file, another host on
the network ...

So if you use klogd and syslogd together you can have kernel log message (also
on console if you like) and the other interrupts are not blocked by
printk.

Mike

--
Dr. Michael Neuhauser                        Phone: +43(1)8958499/17
g.a.m.s. edv-dienstleistungen gmbh           Fax:   +43(1)8958499/60
Stiegergasse 15-17/8                         Email: mike at gams.at
A-1150 Vienna/Austria/Europe


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/