[CRIU] [PATCH] [RFC] perf: Here is an example how to trace syscalls
Christopher Covington
cov at codeaurora.org
Mon Oct 6 06:30:02 PDT 2014
On 10/01/2014 04:03 AM, Andrew Vagin wrote:
> On Tue, Sep 30, 2014 at 01:23:55PM -0400, Christopher Covington wrote:
>> On 09/30/2014 08:05 AM, Andrey Vagin wrote:
>>> perf doesn't affect performance so significant as strace and
>>> it allows to trace parasite code.
>>>
>>> All processes are executed in a new perf_evets cgroup and
>>> "perf record" collects events only for processes from this group.
>>
>> Why do you need container based monitoring instead of just command-and-childen
>> based with `perf record $CRIU_CPT`?
>
> I want to trace parasite code, which is injected in dumped processes.
I think putting this in the commit message and/or comments would be helpful.
How do you differentiate parasite versus pre-parasite/post-parasite original code?
Thanks,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
More information about the CRIU
mailing list