Event logging vs enhancing printk
Michael Holzheu wrote...
Quoted 3 lines
I think it would be important to have both options:
feed printk messages into posix event logging (this does the current patch as far as I know)
The current patch forks the message to evlog inside the printk function. This thread is proposing that the printk function be wrapped inside a macro so you could easily capture file/funcname/lineno of the calling function along with the original printk message
(plus the other stuff stored in the evlog record header).
Quoted 3 lines
AND feed events
which are written with the new posix event APIs into the traditional syslogd logging.
This would be done in user-space, not in the kernel. This is on our enhancements list for event logging.