Hi Frantisek,
"
So, I would like to clarify. Should the pager hold the output from kconsole
commands only?
"
Clearly we want output of a typical kernel command (tasks) to be paged. But
we don't want paging for klog system call or any normal kernel message
(fault, panic, etc). Commands like test* which run for a long time and spawn
threads seem to be the corner case.
"
To hold the output from spawned threads a kconsole could be created in its
own task and instead of checking thread id a task id would be checked?
"
That does not sound like a very clean solution to me.
"
That means output is blocked on specified number of lines but debug text
from other threads is still shown. Or should the pager hold all output
written to kconsole from any thread but pass it to klog so uspace could
retrieve it?
"
Definitely not.
"
I tried both ways and I have troubles testing the second one, for when I try
to run 'test slab2' in kcon and have running klog in uspace the klog hangs
ultimately.
Or am I missing anything?
"
IMHO only kernel shell command output should be paged. To that end, we
should specify explicitly what should be paged and what should not. For
example. by introducing a new printf-like function. The only question is how
to handle tests, which you usually want to run in a non-interactive way.
Best regards,
Jiri
"
Regards,
Frantisek Haas
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel";
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
