Hi,

Could someone clarify the behaviour of the -p PID flag of perf-record?
In our experiments (3.2.0-27 #43-Ubuntu SMP x86_64),
it ignores events on threads spawned after perf-record is started.
Is this the intended behaviour, and is there any work-around?

Generally, what is the best (vs CPU/IO, distortion of profiling results)
way to record only events of a given OS process, with all its threads?

Thanks a lot,
Mikolaj
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to