"PERF_SAMPLE_REGS_USER is not yet supported" fatal error on perf.data recorded with `--call-graph dwarf` about perf_data_converter HOT 3 CLOSED

I was kinda hoping we could ignore PERF_SAMPLE_REGS_USER if it's not supported yet, like we do for UNKNOWN_EVENT_17.

from perf_data_converter.

I have the same issue on the current latest master commit:

aris@linux:~/sources/perf_data_converter$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.3 LTS
Release:	20.04
Codename:	focal
aris@linux:~/sources/perf_data_converter$ perf --version
perf version 5.4.189
aris@linux:~/sources/perf_data_converter$ git rev-parse HEAD
3a630ff16ba6a8ba8e834d9a2acf3f06a879cadf

I run

perf record --call-graph=dwarf -p `pidof mserver5`

which works fine, e.g. I can transform all of this into a nice flamegraph following Brendan Gregg's approach. But I prefer to use KCachegrind for this kind of profile analysis. I have succesfully used gperftools to do this. Now I am trying a similar route with perf_stat.

But as for this tool, the error happens both with default strictest setting (3) for /proc/sys/kernel/perf_event_paranoid which requires me to use sudo to execute perf command and which gives similar output as @mhansen and it happens with the most relaxed setting (-1). Although with the most relaxed setting, I have less output:

aris@linux:~/sources/monetdb/default$ perf_to_profile -i perf.data -o data.prof
[WARNING:src/quipper/perf_reader.cc:1320] Skipping 104 bytes of metadata: HEADER_CPU_TOPOLOGY
[WARNING:src/quipper/perf_reader.cc:1067] Skipping unsupported event PERF_RECORD_CPU_MAP
[ERROR:src/quipper/sample_info_reader.cc:402] PERF_SAMPLE_REGS_USER is not yet supported.
[ERROR:src/quipper/perf_reader.cc:1051] Couldn't read event PERF_RECORD_SAMPLE
[ERROR:src/perf_data_converter.cc:749] Could not read input perf.data
[FATAL:src/perf_to_profile.cc:33] Expected profile vector to have one element.

from perf_data_converter.

To clarify the current state:

At Google we do not use collection modes that can result in user mode register values to be recorded in the perf.data file. Hence the priority for us to work on this issue is low and we don't anticipate addressing or triaging it further soon.

from perf_data_converter.