[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190212130930.GN775@krava>
Date: Tue, 12 Feb 2019 14:09:30 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Alexey Budankov <alexey.budankov@...ux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Andi Kleen <ak@...ux.intel.com>,
linux-kernel <linux-kernel@...r.kernel.org>
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
Powered by blists - more mailing lists