* David Ahern <dsah...@gmail.com> wrote:
> On 9/9/13 7:03 AM, Jiri Olsa wrote:
> >my usage currently is to having this running during the day:
> >(well whenever I remember to run it.. ;-) )
> >
> > [jolsa@krava perf]$ sudo ./perf record -g -M 1m -a
> >
> >and checking report when the system or app get stuck
> >
> >with multiple files I can just easily (or automaticaly)
> >remove old ones without restarting session
>
> Aren't you losing potentially important events by doing that -- FORK,
> COMM, MMAP?
I suspect these could/should be tracked and emitted fully (in bulk) when a
new data file is opened, so that each partial data file is fully
consistent?
> I have a flight recorder style command that address this problem
> (long-running/daemons) by processing task events and then stashing the
> sample events on a time-ordered list with chopping to maintain the time
> window.
Could this be used to emit currently relevant task context?
Btw., I also think it would be useful to have kernel support for that -
the 'collections' stuff I talked about a good while ago: the kernel would
work with user-space to iterate over all MMAPs and all running COMMs at
the opening of a tracing session.
That way we could avoid racy access to /proc, we could make sure that all
information that is emitted by FORK/COMM/MMAP is also emitted for the
'bulk' data, etc.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
