[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ee1c9b6-516f-cee1-1b37-388fb5507cd3@huawei.com>
Date: Wed, 2 Dec 2020 00:28:18 +0300
From: Alexei Budankov <abudankov@...wei.com>
To: Jiri Olsa <jolsa@...hat.com>, Petr Malat <oss@...at.biz>,
<alexey.v.bayduraev@...ux.intel.com>
CC: <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Namhyung Kim <namhyung@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>, <abudankov@...wei.com>
Subject: Re: [PATCH v2 1/3] Revert "perf session: Fix decompression of
PERF_RECORD_COMPRESSED records"
Eventually sending to the proper Alexey's address.
On 02.12.2020 0:04, Alexei Budankov wrote:
>
> On 01.12.2020 22:09, Jiri Olsa wrote:
>> On Mon, Nov 30, 2020 at 12:40:20PM +0100, Petr Malat wrote:
>>> Hi Jiří,
>>> were you able to reproduce the issue? I may also upload perf-archive
>>> if that would help.
>>
>> oh yea ;-) seems like those 2 commits you reverted broke 32 bits
>> perf for data files > 32MB
>>
>> but the fix you did does not work for Alexey's test he mentioned
>> in the commit:
>>
>> $ perf record -z -- some_long_running_workload
>> $ perf report --stdio -vv
>>
>> it's failing for me with:
>>
>> # ./perf report
>> Couldn't allocate memory for decompression
>> 0xfe6f3a [0x60]: failed to process type: 81 [Operation not permitted]
>> Error:
>> failed to process sample
>> # To display the perf.data header info, please use --header/--header-only options.
>> #
>>
>> I think that's why here's special handling for compressed
>> events, but I'll need to check on that in more detail,
>> I was hoping for Alexey to answer ;-)
>
> Sorry for delay. Alexey Bayduraev could possibly help with that sooner.
> Alexey, could you please follow up.
>
> Thanks,
> Alexei
Powered by blists - more mailing lists