Hi, Thanks for your reply.
> The second waitpid() near the end is to reclaim the child's resources. > And yes, the counters values (perfmon2 state) remains available until > the last file descriptor on it closes. So what is the context actually inside the kernel? I can see that it is used in all calls to access the PMUs registers through its file descriptor, but I guess it is not a "regular" file, is it? Cheers, Andrej ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
