On Thu, Mar 26, 2020 at 02:07:39AM +0430, ahmadkhorrami wrote: > Here is the link for the gmallocn() case: > https://gofile.io/?c=o95O7N > The output for the second case is big. I have a small one produced several > days ago the link of which is as follows: > https://gofile.io/?c=OIPCjx looking good, but I still need you t run 'perf archive' on top of your data and send me the perf.data.tar.bz2 it generates, like: [jolsa@krava perf]$ sudo ./perf record ^C[ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 1.675 MB perf.data (6248 samples) ] [jolsa@krava perf]$ sudo ./perf archive Now please run: $ tar xvf perf.data.tar.bz2 -C ~/.debug wherever you need to run 'perf report' on. I need that perf.data.tar.bz2 generated from your data thanks, jirka > Regards. > > On 2020-03-26 01:39, Steven Rostedt wrote: > > > On Wed, 25 Mar 2020 22:02:52 +0100 > > Jiri Olsa <jolsa@xxxxxxxxxx> wrote: > > > > > yea, no luck.. so if you could generate some reasonable small > > > perf.data that > > > shows the issue and send it over together with 'perf archive' data > > > privately > > > to me and to whoever else ask for it, so we don't polute the list.. > > > > Right. And it may be better if you compress it too. > > > > xz perf.data > > > > and attach the perf.data.xz (and only privately send it to Mr. Olsa). > > > > -- Steve > > > > > or if you could put it somewhere on the web/ftp.. that'd be best >
|