Re: How can I user @cast in the user-space's program or have other ways to aasign valus to the user-space pointer to a structure.

) printf(call--call\n) } -- David Smith dsm...@redhat.com Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)

Re: [PATCH 1/4] ptrace: temporary revert the recent ptrace/jobctl rework

-utrace code to handle the new ptrace changes. -- David Smith dsm...@redhat.com Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)

Re: resuming after stop at syscall_entry

of the API, rather than what makes sense to me who has thought too much already about all this stuff. We should probably just dump your email into the wiki. -- David Smith dsm...@redhat.com Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)

Re: syscall tracing overheads: utrace vs. kprobes

= 0.36 us per hit Note that these are microbenchmarks that represent an ideal case compared to a larger run, since they probably fit comfily inside caches. They probably also undercount the probe handler's run time. -- David Smith dsm...@redhat.com Red Hat http://www.redhat.com 256.217.0141

Re: resuming after stop at syscall_entry

this would make sense to people. -- David Smith dsm...@redhat.com Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)

UTRACE_STOP in exec handler

no difference.) -- David Smith [EMAIL PROTECTED] Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax) #include linux/sched.h #include linux/pid.h #include linux/utrace.h #include linux/err.h #include linux/module.h #include linux/errno.h MODULE_DESCRIPTION(automatic suspend on crash

utrace_set_events in quiesce handler?

anything similar in the current utrace.) Thanks for the help. -- David Smith [EMAIL PROTECTED] Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)

Re: global tracing

apply much. Systemtap is interested in performance impacts and the a./b. advantages seem quite obvious to me. Avoiding the complexities of manually attaching/detaching to every thread in the system seems important also. -- David Smith [EMAIL PROTECTED] Red Hat http://www.redhat.com 256.217.0141

Re: crash-suspend teardown races

(interrupting detach) that we need to eliminate to make the facility acceptable as the basis for pervasive tracing of many processes on the system. Is there a way to avoid using UTRACE_INTERRUPT? Certainly I'd like to avoid disturbing the processes we're tracing. -- David Smith [EMAIL PROTECTED

crash-suspend teardown races

ahead and exit. I'd appreciate any thoughts, criticisms, etc. on this patch, which I've tested under kernel 2.6.27-0.186.rc0.git15.fc10. -- David Smith [EMAIL PROTECTED] Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax) --- /home/dsmith/crash-suspend.c2008-07-30 15:36

Re: utrace doc update, nearing submission(?)

makes lots of sense - I wish it could be included somewhere. So, basically, you do something like this: rc = utrace_control(t, engine, UTRACE_STOP); if (rc == -EINPROGRESS) { rc = utrace_control(t, engine, UTRACE_INTERRUPT); } -- David Smith [EMAIL PROTECTED

crash-suspend.c using new interface

, but triggers a BUG_ON message when the crashed/suspended process is put back in the foreground. Note that I don't have any real feel for whether the bug lies in my crash-suspend.c translation or the new utrace itself. The BUG details are in msg.txt. -- David Smith [EMAIL PROTECTED] Red Hat http

Re: Tracing Syscalls under Fedora 9

the same thing - system call callbacks that got called under F8 aren't getting called under F9. -- David Smith [EMAIL PROTECTED] Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)

need quiesce help

engines get installed on the thread in the same callback. Thanks for the help. -- David Smith [EMAIL PROTECTED] Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)