Hi, Regarding the #91: > > The patch does not compile on all architectures (you can use > ./tools/check.sh to compile HelenOS for all supported targets) - it seems > to me that using %d for sysarg is at fault. > Sorry for that. Will check all archs from now on.
> I was not able to use the pager for some commands. For example, running > pager followed by test slab2 would not invoke the pager correctly (in QEMU > on ia32). > Well, I'm bit confused about that. I talked with Martin Decky about the kernel pager and though that it should not block uspace, e.g. it should hold output only from kconsole thread. And that's what I first implemented. Then I realized that some commands even spawn threads (!= kconsole thread) and that cause those troubles you mention. So, I would like to clarify. Should the pager hold the output from kconsole commands only? 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 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? 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? Regards, Frantisek Haas
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
