Subject: Re: typed copyin/copyout (was: Re: Show sysctl activity in ktrace)
To: None <firstname.lastname@example.org>
From: Christos Zoulas <email@example.com>
Date: 09/21/2006 12:22:28
In article <20060921065023.GS1277@snowdrop.l8s.co.uk>,
David Laight <firstname.lastname@example.org> wrote:
>On Wed, Sep 20, 2006 at 11:36:48PM -0700, Jason Thorpe wrote:
>> If we really want a better ktrace, we should get rid of it completely
>> and instead integrate dtrace from OpenSolaris.
>Certainly something that works the way the SVR4 (and probably solaris)
>'truss' program does  would be better for general monitoring of
>programs - rather than splatting printf calls throughout the kernel.
>Of course you lose the tracing of internal kernel events - eg namei.
> process blocks on syscall entry/exit allowing the tracing process
>to determine the syscall arguments and read (write??) the traced
>processes memory. truss is just a very large nested switch statement
>with lots of printf call - but they are all in userspace.
It is called PT_SYSCALL and we already have it.