On Mon, Sep 09, 2013 at 07:11:11AM -0700, David Ahern 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?
those are synthesized for each file via synthesize_record function, see: [PATCH 19/25] perf tools: Move synthesizing into single function > > 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. so far I noticed there could be race among EXIT and remaining SAMPLE events on another CPU mmap than EXIT event.. ending up with EXIT being stored in the old file, while SAMPLEs will get to the new one I was thinking about some 'perf daemon' so I dont need to run that manually.. seems similar to what you did jirka -- 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/
