updated to dump data from read and write system calls, just to show how it's done.
If this looks ok it's not a big deal to add symbolic dumps of stuff like open modes, etc. in the limit we can drive the trace overhead per target system call to below one. The plan 9 work I did got it down to about 4, lower than the strace ratio of about 25. It also means, now that we can export file systems from akaros, that on a linux system, stracing an akaros process works like this: import akaros /proc akproc cat akproc/pid/strace All done. Distributed systems are nice. Unix, come to think of it, is a nice model. The following changes since commit 915eac00a7e0f578f9e921af2b205b6efa3739b5: Slices: A growable list of pointers. (2016-01-25 11:02:20 -0500) are available in the git repository at: [email protected]:rminnich/akaros strace for you to fetch changes up to 070b569c2962e98c2a645837fb5a332c31ac2f32: New and easy strace framework. (2016-01-25 17:39:24 -0800) ---------------------------------------------------------------- Ronald G. Minnich (1): New and easy strace framework. kern/drivers/dev/proc.c | 25 +++++++++++ kern/include/env.h | 5 +++ kern/src/process.c | 5 +++ kern/src/syscall.c | 112 ++++++++++++++++++++++++++++++++++++++++-------- 4 files changed, 128 insertions(+), 19 deletions(-) https://github.com/rminnich/akaros/compare/rminnich:master...strace -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
