On Sun, May 26, 2013 at 4:48 PM, Hopsing K <hopsi...@gmail.com> wrote: > Hi, Ok, thanks. I got a little better picture. Is the following true: > - The ptrace-ing parent waits in waitpid() called from within the > userspace() loops.
Correct. > - The SIGVTALRM comes in and the signal handler is executed, it'll end up > in scheduler_tick() and set need_resched() true. Yeah. We use SIGVTALRM timer tick. > - Because of the signal the waitpid() system call is interrupted and the > ptrace-ing parent returnes from waitpid(). Correct. > - At the same time the ptraced userspace slave is stopped (is this the > case?) therefore the condition WIFSTOPPED(status) is true and > therefore you end up calling interrupt_end() ? Correct. -- Thanks, //richard ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
