Messages in this thread | | | Date | Sun, 12 Sep 2021 22:44:12 +0200 | From | Jiri Olsa <> | Subject | Re: [PATCH v11 00/24] Introduce threaded trace streaming for basic perf record operation |
| |
On Tue, Aug 17, 2021 at 11:23:03AM +0300, Alexey Bayduraev wrote:
SNIP
> > Alexey Bayduraev (24): > perf record: Introduce thread affinity and mmap masks > tools lib: Introduce fdarray duplicate function > perf record: Introduce thread specific data array > perf record: Introduce function to propagate control commands > perf record: Introduce thread local variable > perf record: Stop threads in the end of trace streaming > perf record: Start threads in the beginning of trace streaming > perf record: Introduce data file at mmap buffer object > perf record: Introduce bytes written stats to support --max-size > option > perf record: Introduce data transferred and compressed stats > perf record: Init data file at mmap buffer object > perf record: Introduce --threads command line option > perf record: Extend --threads command line option > perf record: Implement compatibility checks > perf report: Output non-zero offset for decompressed records > perf report: Output data file name in raw trace dump
following patches:
> perf session: Move reader structure to the top > perf session: Introduce reader_state in reader object > perf session: Introduce reader objects in session object > perf session: Introduce decompressor into trace reader object > perf session: Move init into reader__init function > perf session: Move map/unmap into reader__mmap function > perf session: Load single file for analysis
up to here
are changing the core of processing perf.data files, I think they should be submitted in separate patchset first and some tests for that would be great
jirka
| |