| Date | Tue, 12 Feb 2019 14:09:30 +0100 | From | Jiri Olsa <> | Subject | Re: [PATCH v2 4/4] perf report: support record trace file decompression |
| |
On Mon, Feb 11, 2019 at 11:25:00PM +0300, Alexey Budankov wrote:
SNIP
> @@ -1932,6 +2059,38 @@ fetch_mmaped_event(struct perf_session *session, > return event; > } > > +static int __perf_session__process_decomp_events(struct perf_session *session) > +{ > + s64 skip; > + u64 size, file_pos = 0; > + union perf_event *event; > + struct decomp *decomp = session->decomp_last; > + > + if (!decomp) > + return 0; > + > + while (decomp->head < decomp->size && !session_done()) {
so how this actualy works? does one PERF_RECORD_COMPRESSED event carry complete data to unpack? or you wait to receive more PERF_RECORD_COMPRESSED to give you data you can unpack?
jirka
|