perf record: Add 8-byte aligned event type PERF_RECORD_COMPRESSED2
PATCH v2 1/2 perf record: Add 8-byte aligned event type PERF_RECORD_COMPRESSED2
The original PERF_RECORD_COMPRESS is not 8-byte aligned, which can cause asan runtime error:
# Build with asan
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined"
# Test success with many asan runtime errors:
$ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv
83: Zstd perf.data compression/decompression:
...
util/session.c:1959:13: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 13 byte alignment
0x7f69e3f99653: note: pointer points here
d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00
^
util/session.c:2163:22: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 8 byte alignment
0x7f69e3f99653: note: pointer points here
d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00
^
...Since there is no way to align compressed data in zstd compression, this patch add a new event type PERF_RECORD_COMPRESSED2, which adds a field data_size to specify the actual compressed data size. The header.size contains the total record size, including the padding at the end to make it 8-byte aligned.
Tested with Zstd perf.data compression/decompression
---
v2:
Add deprecated comment for PERF_RECORD_COMPRESSED.
tools/lib/perf/Documentation/libperf.txt | 1 + tools/lib/perf/include/perf/event.h | 12 ++++++++++ .../Documentation/perf.data-file-format.txt | 24 +++++++++++++++---- tools/perf/builtin-record.c | 23 ++++++++++++++---- tools/perf/util/event.c | 1 + tools/perf/util/session.c | 5 +++- tools/perf/util/tool.c | 11 +++++++-- 7 files changed, 64 insertions(+), 13 deletions(-)
tools/lib/perf/Documentation/libperf.txt +1 -0
@@ -210,6 +210,7 @@ SYNOPSIS struct perf_record_time_conv; struct perf_record_header_feature; struct perf_record_compressed; + struct perf_record_compressed2; -- DESCRIPTION
tools/lib/perf/include/perf/event.h +12 -0
@@ -457,6 +457,16 @@ struct perf_record_compressed {char data[]; }; +/* +* `header.size` includes the padding we are going to add while writing the record. +* `data_size` only includes the size of `data[]` itself. +*/ +struct perf_record_compressed2 { +struct perf_event_header header; +__u64 data_size; +char data[]; +}; +enum perf_user_event_type {/* above any possible kernel type */ PERF_RECORD_USER_TYPE_START =64 ,PERF_RECORD_HEADER_ATTR =64 ,
@@ -478,6 +488,7 @@ enum perf_user_event_type { /* above any possible kernel type */PERF_RECORD_HEADER_FEATURE =80 ,PERF_RECORD_COMPRESSED =81 ,PERF_RECORD_FINISHED_INIT =82 , +PERF_RECORD_COMPRESSED2 =83 , PERF_RECORD_HEADER_MAX };
@@ -518,6 +529,7 @@ union perf_event {struct perf_record_time_conv time_conv;struct perf_record_header_feature feat;struct perf_record_compressed pack; + struct perf_record_compressed2 pack2; };#endif /* __LIBPERF_EVENT_H */
tools/perf/Documentation/perf.data-file-format.txt +19 -5
@@ -370,7 +370,7 @@ struct { u32 mmap_len; }; -Indicates that trace contains records of PERF_RECORD_COMPRESSED type +Indicates that trace contains records of PERF_RECORD_COMPRESSED2 type that have perf_events records in compressed form. HEADER_CPU_PMU_CAPS = 28,
@@ -602,7 +602,14 @@ struct auxtrace_error_event { Describes a header feature. These are records used in pipe-mode that contain information that otherwise would be in perf.data file's header. - PERF_RECORD_COMPRESSED = 81, + PERF_RECORD_COMPRESSED = 81, /* deprecated */ + +The header is followed by compressed data frame that can be decompressed +into array of perf trace records. The size of the entire compressed event +record including the header is limited by the max value of header.size. + +It is deprecated and new files should use PERF_RECORD_COMPRESSED2 to gurantee +8-byte alignment. struct compressed_event { struct perf_event_header header;
@@ -618,10 +625,17 @@ This is used, for instance, to 'perf inject' events after init and before regular events, those emitted by the kernel, to support combining guest and host records. + PERF_RECORD_COMPRESSED2 = 83, -The header is followed by compressed data frame that can be decompressed -into array of perf trace records. The size of the entire compressed event -record including the header is limited by the max value of header.size. +8-byte aligned version of `PERF_RECORD_COMPRESSED`. `header.size` indicates the +total record size, including padding for 8-byte alignment, and `data_size` +specifies the actual size of the compressed data. + +struct perf_record_compressed2 { + struct perf_event_header header; + __u64 data_size; + char data[]; +}; Event types
tools/perf/builtin-record.c +18 -5
@@ -648,14 +648,27 @@ static int record__pushfn(struct mmap *map, void *to, void *bf, size_t size)struct record *rec = to;if (record__comp_enabled (rec)) { +struct perf_record_compressed2 *event = map->data; +size_t padding =0 ; +u8 pad[8 ] = {0 };ssize_t compressed =zstd_compress (rec->session, map, map->data,mmap__mmap_len (map), bf, size);if (compressed <0 )return (int )compressed; - size = compressed; - bf = map->data; + bf = event; + thread->samples++; + +/* +* The record from `zstd_compress` is not 8 bytes aligned, which would cause asan +* error. We make it aligned here. +*/ + event->data_size = compressed -sizeof (struct perf_record_compressed2 ); + event->header.size =PERF_ALIGN (compressed,sizeof (u64)); + padding = event->header.size - compressed; +return record__write (rec, map, bf, compressed) || +record__write (rec, map, &pad, padding); } thread->samples++;
@@ -1534,7 +1547,7 @@ static void record__adjust_affinity(struct record *rec, struct mmap *map)static size_t process_comp_header (void *record,size_t increment) { -struct perf_record_compressed *event = record; +struct perf_record_compressed2 *event = record;size_t size =sizeof (*event);if (increment) {
@@ -1542,7 +1555,7 @@ static size_t process_comp_header(void *record, size_t increment)return increment; } - event->header.type =PERF_RECORD_COMPRESSED ; + event->header.type =PERF_RECORD_COMPRESSED2 ; event->header.size = size;return size;
@@ -1552,7 +1565,7 @@ static ssize_t zstd_compress(struct perf_session *session, struct mmap *map, void *dst, size_t dst_size, void *src, size_t src_size) { ssize_t compressed; -size_t max_record_size =PERF_SAMPLE_MAX_SIZE -sizeof (struct perf_record_compressed ) -1 ; +size_t max_record_size =PERF_SAMPLE_MAX_SIZE -sizeof (struct perf_record_compressed2 ) -1 ;struct zstd_data *zstd_data = &session->zstd_data;if (map && map->file)
tools/perf/util/event.c +1 -0
@@ -77,6 +77,7 @@ static const char *perf_event__names[] = { [PERF_RECORD_HEADER_FEATURE] = "FEATURE", [PERF_RECORD_COMPRESSED] = "COMPRESSED", [PERF_RECORD_FINISHED_INIT] = "FINISHED_INIT", + [PERF_RECORD_COMPRESSED2] = "COMPRESSED2", };const char *perf_event__name (unsigned int id)
tools/perf/util/session.c +4 -1
@@ -1400,7 +1400,9 @@ static s64 perf_session__process_user_event(struct perf_session *session,int err;perf_sample__init (&sample,/*all=*/ true); -if (event->header.type !=PERF_RECORD_COMPRESSED ||perf_tool__compressed_is_stub (tool)) +if ((event->header.type !=PERF_RECORD_COMPRESSED && + event->header.type !=PERF_RECORD_COMPRESSED2 ) || +perf_tool__compressed_is_stub (tool))dump_event (session->evlist, event, file_offset, &sample, file_path);/* These events are processed right away */
@@ -1481,6 +1483,7 @@ static s64 perf_session__process_user_event(struct perf_session *session, err = tool->feature (session, event);break ;case PERF_RECORD_COMPRESSED : +case PERF_RECORD_COMPRESSED2 : err = tool->compressed (session, event, file_offset, file_path);if (err)dump_event (session->evlist, event, file_offset, &sample, file_path);
tools/perf/util/tool.c +9 -2
@@ -43,8 +43,15 @@ static int perf_session__process_compressed_event(struct perf_session *session, decomp->size = decomp_last_rem; } - src = (void *)event +sizeof (struct perf_record_compressed ); - src_size = event->pack.header.size -sizeof (struct perf_record_compressed ); +if (event->header.type ==PERF_RECORD_COMPRESSED ) { + src = (void *)event +sizeof (struct perf_record_compressed ); + src_size = event->pack.header.size -sizeof (struct perf_record_compressed ); + }else if (event->header.type ==PERF_RECORD_COMPRESSED2 ) { + src = (void *)event +sizeof (struct perf_record_compressed2 ); + src_size = event->pack2.data_size; + }else { +return -1 ; + } decomp_size =zstd_decompress_stream (session->active_decomp->zstd_decomp, src, src_size, &(decomp->data[decomp_last_rem]), decomp_len - decomp_last_rem);
--
2.48.1.711.g2feabab25a-goog
PATCH v2 2/2 perf record: Fix a asan runtime error in util/maps.c
If I build perf with asan and run Zstd test:
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined" $ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv 83: Zstd perf.data compression/decompression: ... util/maps.c:1046:5: runtime error: null pointer passed as argument 2, which is declared to never be null ...
The issue was caused by bsearch. The patch adds a check to ensure argument 2 and 3 are not NULL and 0.
Testing with the commands above confirms that the runtime error is resolved.
--- tools/perf/util/maps.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
tools/perf/util/maps.c +6 -3
@@ -1042,10 +1042,13 @@ struct map *maps__find(struct maps *maps, u64 ip)while (!done) {down_read (maps__lock (maps));if (maps__maps_by_address_sorted (maps)) { -struct map **mapp = -bsearch (&ip,maps__maps_by_address (maps),maps__nr_maps (maps), -sizeof (*mapp), map__addr_cmp); +struct map **mapp =NULL ; +struct map **maps_by_address =maps__maps_by_address (maps); +unsigned int nr_maps =maps__nr_maps (maps); +if (maps_by_address && nr_maps) + mapp =bsearch (&ip, maps_by_address, nr_maps,sizeof (*mapp), + map__addr_cmp);if (mapp) result =map__get (*mapp); done = true;
Signature · 1 line
2.48.1.711.g2feabab25a-goog
Namhyung Kim
maintainerHello,
Quoted 19 lines · Chun-Tse Shao
The original
PERF_RECORD_COMPRESSis not 8-byte aligned, which can cause asan runtime error:# Build with asan
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined" # Test success with many asan runtime errors: $ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv 83: Zstd perf.data compression/decompression: ... util/session.c:1959:13: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 13 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ util/session.c:2163:22: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 8 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ ...
Quoted 7 lines
Since there is no way to align compressed data in zstd compression, this patch add a new event type
PERF_RECORD_COMPRESSED2, which adds a fielddata_sizeto specify the actual compressed data size. Theheader.sizecontains the total record size, including the padding at the end to make it 8-byte aligned.Tested with
Zstd perf.data compression/decompression
Looks good to me.
Arnaldo, are you ok with adding a new record type for this?
Thanks,
Namhyung
Quoted 235 lines
Signed-off-by Chun-Tse Shao <[email protected]>---
v2:
Add deprecated comment forPERF_RECORD_COMPRESSED.tools/lib/perf/Documentation/libperf.txt | 1 + tools/lib/perf/include/perf/event.h | 12 ++++++++++ .../Documentation/perf.data-file-format.txt | 24 +++++++++++++++---- tools/perf/builtin-record.c | 23 ++++++++++++++---- tools/perf/util/event.c | 1 + tools/perf/util/session.c | 5 +++- tools/perf/util/tool.c | 11 +++++++-- 7 files changed, 64 insertions(+), 13 deletions(-)tools/lib/perf/Documentation/libperf.txt +1
-0@@ -210,6 +210,7 @@ SYNOPSIS struct perf_record_time_conv; struct perf_record_header_feature; struct perf_record_compressed; + struct perf_record_compressed2; -- DESCRIPTIONtools/lib/perf/include/perf/event.h +12
-0@@ -457,6 +457,16 @@ struct perf_record_compressed {char data[]; }; +/* +* `header.size` includes the padding we are going to add while writing the record. +* `data_size` only includes the size of `data[]` itself. +*/ +struct perf_record_compressed2 { +struct perf_event_header header; +__u64 data_size; +char data[]; +}; +enum perf_user_event_type {/* above any possible kernel type */ PERF_RECORD_USER_TYPE_START =64 ,PERF_RECORD_HEADER_ATTR =64 ,@@ -478,6 +488,7 @@ enum perf_user_event_type { /* above any possible kernel type */PERF_RECORD_HEADER_FEATURE =80 ,PERF_RECORD_COMPRESSED =81 ,PERF_RECORD_FINISHED_INIT =82 , +PERF_RECORD_COMPRESSED2 =83 , PERF_RECORD_HEADER_MAX };@@ -518,6 +529,7 @@ union perf_event {struct perf_record_time_conv time_conv;struct perf_record_header_feature feat;struct perf_record_compressed pack; + struct perf_record_compressed2 pack2; };#endif /* __LIBPERF_EVENT_H */ tools/perf/Documentation/perf.data-file-format.txt +19
-5@@ -370,7 +370,7 @@ struct { u32 mmap_len; }; -Indicates that trace contains records of PERF_RECORD_COMPRESSED type +Indicates that trace contains records of PERF_RECORD_COMPRESSED2 type that have perf_events records in compressed form. HEADER_CPU_PMU_CAPS = 28,@@ -602,7 +602,14 @@ struct auxtrace_error_event { Describes a header feature. These are records used in pipe-mode that contain information that otherwise would be in perf.data file's header. - PERF_RECORD_COMPRESSED = 81, + PERF_RECORD_COMPRESSED = 81, /* deprecated */ + +The header is followed by compressed data frame that can be decompressed +into array of perf trace records. The size of the entire compressed event +record including the header is limited by the max value of header.size. + +It is deprecated and new files should use PERF_RECORD_COMPRESSED2 to gurantee +8-byte alignment. struct compressed_event { struct perf_event_header header;@@ -618,10 +625,17 @@ This is used, for instance, to 'perf inject' events after init and before regular events, those emitted by the kernel, to support combining guest and host records. + PERF_RECORD_COMPRESSED2 = 83, -The header is followed by compressed data frame that can be decompressed -into array of perf trace records. The size of the entire compressed event -record including the header is limited by the max value of header.size. +8-byte aligned version of `PERF_RECORD_COMPRESSED`. `header.size` indicates the +total record size, including padding for 8-byte alignment, and `data_size` +specifies the actual size of the compressed data. + +struct perf_record_compressed2 { + struct perf_event_header header; + __u64 data_size; + char data[]; +}; Event typestools/perf/builtin-record.c +18
-5@@ -648,14 +648,27 @@ static int record__pushfn(struct mmap *map, void *to, void *bf, size_t size)struct record *rec = to;if (record__comp_enabled (rec)) { +struct perf_record_compressed2 *event = map->data; +size_t padding =0 ; +u8 pad[8 ] = {0 };ssize_t compressed =zstd_compress (rec->session, map, map->data,mmap__mmap_len (map), bf, size);if (compressed <0 )return (int )compressed; - size = compressed; - bf = map->data; + bf = event; + thread->samples++; + +/* +* The record from `zstd_compress` is not 8 bytes aligned, which would cause asan +* error. We make it aligned here. +*/ + event->data_size = compressed -sizeof (struct perf_record_compressed2 ); + event->header.size =PERF_ALIGN (compressed,sizeof (u64)); + padding = event->header.size - compressed; +return record__write (rec, map, bf, compressed) || +record__write (rec, map, &pad, padding); } thread->samples++;@@ -1534,7 +1547,7 @@ static void record__adjust_affinity(struct record *rec, struct mmap *map)static size_t process_comp_header (void *record,size_t increment) { -struct perf_record_compressed *event = record; +struct perf_record_compressed2 *event = record;size_t size =sizeof (*event);if (increment) {@@ -1542,7 +1555,7 @@ static size_t process_comp_header(void *record, size_t increment)return increment; } - event->header.type =PERF_RECORD_COMPRESSED ; + event->header.type =PERF_RECORD_COMPRESSED2 ; event->header.size = size;return size;@@ -1552,7 +1565,7 @@ static ssize_t zstd_compress(struct perf_session *session, struct mmap *map, void *dst, size_t dst_size, void *src, size_t src_size) { ssize_t compressed; -size_t max_record_size =PERF_SAMPLE_MAX_SIZE -sizeof (struct perf_record_compressed ) -1 ; +size_t max_record_size =PERF_SAMPLE_MAX_SIZE -sizeof (struct perf_record_compressed2 ) -1 ;struct zstd_data *zstd_data = &session->zstd_data;if (map && map->file)tools/perf/util/event.c +1
-0@@ -77,6 +77,7 @@ static const char *perf_event__names[] = { [PERF_RECORD_HEADER_FEATURE] = "FEATURE", [PERF_RECORD_COMPRESSED] = "COMPRESSED", [PERF_RECORD_FINISHED_INIT] = "FINISHED_INIT", + [PERF_RECORD_COMPRESSED2] = "COMPRESSED2", };const char *perf_event__name (unsigned int id)tools/perf/util/session.c +4
-1@@ -1400,7 +1400,9 @@ static s64 perf_session__process_user_event(struct perf_session *session,int err;perf_sample__init (&sample,/*all=*/ true); -if (event->header.type !=PERF_RECORD_COMPRESSED ||perf_tool__compressed_is_stub (tool)) +if ((event->header.type !=PERF_RECORD_COMPRESSED && + event->header.type !=PERF_RECORD_COMPRESSED2 ) || +perf_tool__compressed_is_stub (tool))dump_event (session->evlist, event, file_offset, &sample, file_path);/* These events are processed right away */ @@ -1481,6 +1483,7 @@ static s64 perf_session__process_user_event(struct perf_session *session, err = tool->feature (session, event);break ;case PERF_RECORD_COMPRESSED : +case PERF_RECORD_COMPRESSED2 : err = tool->compressed (session, event, file_offset, file_path);if (err)dump_event (session->evlist, event, file_offset, &sample, file_path);tools/perf/util/tool.c +9
-3@@ -43,8 +43,15 @@ static int perf_session__process_compressed_event(struct perf_session *session, decomp->size = decomp_last_rem; } - src = (void *)event +sizeof (struct perf_record_compressed ); - src_size = event->pack.header.size -sizeof (struct perf_record_compressed ); +if (event->header.type ==PERF_RECORD_COMPRESSED ) { + src = (void *)event +sizeof (struct perf_record_compressed ); + src_size = event->pack.header.size -sizeof (struct perf_record_compressed ); + }else if (event->header.type ==PERF_RECORD_COMPRESSED2 ) { + src = (void *)event +sizeof (struct perf_record_compressed2 ); + src_size = event->pack2.data_size; + }else { +return -1 ; + } decomp_size =zstd_decompress_stream (session->active_decomp->zstd_decomp, src, src_size, &(decomp->data[decomp_last_rem]), decomp_len - decomp_last_rem); --2.48.1.711.g2feabab25a-goog
Arnaldo Carvalho de Melo
maintainerQuoted 28 lines · Namhyung Kim
Hello,
Quoted 25 lines · Chun-Tse Shao
The original
PERF_RECORD_COMPRESSis not 8-byte aligned, which can cause asan runtime error:# Build with asan
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined" # Test success with many asan runtime errors: $ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv 83: Zstd perf.data compression/decompression: ... util/session.c:1959:13: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 13 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ util/session.c:2163:22: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 8 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ ...Since there is no way to align compressed data in zstd compression, this patch add a new event type
PERF_RECORD_COMPRESSED2, which adds a fielddata_sizeto specify the actual compressed data size. Theheader.sizecontains the total record size, including the padding at the end to make it 8-byte aligned.
Quoted 5 lines
Quoted 1 line
Tested with
Zstd perf.data compression/decompressionLooks good to me.
Arnaldo, are you ok with adding a new record type for this?
Checking the discussion and the patch.
- ARnaldo
Arnaldo Carvalho de Melo
maintainerQuoted 27 lines · Arnaldo Carvalho de Melo
Quoted 25 lines · Namhyung Kim
Quoted 24 lines · Chun-Tse Shao
The original
PERF_RECORD_COMPRESSis not 8-byte aligned, which can cause asan runtime error:# Build with asan
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined" # Test success with many asan runtime errors: $ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv 83: Zstd perf.data compression/decompression: ... util/session.c:1959:13: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 13 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ util/session.c:2163:22: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 8 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ ...Since there is no way to align compressed data in zstd compression, this patch add a new event type
PERF_RECORD_COMPRESSED2, which adds a fielddata_sizeto specify the actual compressed data size. Theheader.sizecontains the total record size, including the padding at the end to make it 8-byte aligned.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Tested with
Zstd perf.data compression/decompressionLooks good to me.
Arnaldo, are you ok with adding a new record type for this?
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?
Having some session output showing how an older perf binary handles PERF_RECORD_COMPRESS2 would be informative.
I'll try to reproduce/test this all...
- Arnaldo
Ian Rogers
reviewerQuoted 42 lines · Arnaldo Carvalho de Melo
Quoted 27 lines · Arnaldo Carvalho de Melo
Quoted 25 lines · Namhyung Kim
Quoted 24 lines · Chun-Tse Shao
The original
PERF_RECORD_COMPRESSis not 8-byte aligned, which can cause asan runtime error:# Build with asan
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined" # Test success with many asan runtime errors: $ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv 83: Zstd perf.data compression/decompression: ... util/session.c:1959:13: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 13 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ util/session.c:2163:22: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 8 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ ...Since there is no way to align compressed data in zstd compression, this patch add a new event type
PERF_RECORD_COMPRESSED2, which adds a fielddata_sizeto specify the actual compressed data size. Theheader.sizecontains the total record size, including the padding at the end to make it 8-byte aligned.Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Tested with
Zstd perf.data compression/decompressionLooks good to me.
Arnaldo, are you ok with adding a new record type for this?
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?
Quoted 4 lines
Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.I'll try to reproduce/test this all...
I'm not sure we've worried about old perfs being able to read new perf.data files, but we've worried about new perfs being able to read old perf.data files. So if a change is additive, which this change is, then nothing should be impacted.
My thoughts are this way as this patch:
https://lore.kernel.org/all/[email protected]/
changed most perf.data cpumap encodings in a way that old perfs won't be able to handle.
Perhaps testing/documentation should be present for this kind of thing.
Thanks,
Ian
Arnaldo Carvalho de Melo
maintainerQuoted 45 lines · Ian Rogers
Quoted 44 lines · Arnaldo Carvalho de Melo
Quoted 27 lines · Arnaldo Carvalho de Melo
Quoted 25 lines · Namhyung Kim
Quoted 24 lines · Chun-Tse Shao
The original
PERF_RECORD_COMPRESSis not 8-byte aligned, which can cause asan runtime error:# Build with asan
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined" # Test success with many asan runtime errors: $ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv 83: Zstd perf.data compression/decompression: ... util/session.c:1959:13: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 13 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ util/session.c:2163:22: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 8 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ ...Since there is no way to align compressed data in zstd compression, this patch add a new event type
PERF_RECORD_COMPRESSED2, which adds a fielddata_sizeto specify the actual compressed data size. Theheader.sizecontains the total record size, including the padding at the end to make it 8-byte aligned.Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Tested with
Zstd perf.data compression/decompressionLooks good to me.
Arnaldo, are you ok with adding a new record type for this?
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.
Quoted 6 lines
Quoted 1 line
I'll try to reproduce/test this all...
I'm not sure we've worried about old perfs being able to read new perf.data files, but we've worried about new perfs being able to read old perf.data files. So if a change is additive, which this change is, then nothing should be impacted.
Right, its difficult to make it work both ways, even with testing, but by 'work' I mean that new stuff should be ignored by older versions, i.e. records skipped and then the results will surely be different.
So I'm just curious how older tools will handle these new files and to, if not that super difficult, to improve how we handle unknown records so that in the future, when we add new stuff, we mention that this is something not handled, please use a new tool.
Quoted 6 lines
My thoughts are this way as this patch:
https://lore.kernel.org/all/[email protected]/
changed most perf.data cpumap encodings in a way that old perfs won't be able to handle.Perhaps testing/documentation should be present for this kind of thing.
Right, but in this specific case it should be a matter of telling the user that the header.type PERF_RECORD_COMPRESS2 isn't supported and that the user should try and update their tool.
But now back to figuring out how to generate PERF_RECORD_COMPRESS is generated, use it, then apply this patch, and then see if how the old tool copes.
So documentation is also lacking in suggesting that enumerating the steps needed to test before/after is greatly appreciated.
- Arnaldo
Arnaldo Carvalho de Melo
maintainerQuoted 69 lines · Arnaldo Carvalho de Melo
Quoted 45 lines · Ian Rogers
Quoted 44 lines · Arnaldo Carvalho de Melo
Quoted 27 lines · Arnaldo Carvalho de Melo
Quoted 25 lines · Namhyung Kim
Quoted 24 lines · Chun-Tse Shao
The original
PERF_RECORD_COMPRESSis not 8-byte aligned, which can cause asan runtime error:# Build with asan
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined" # Test success with many asan runtime errors: $ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv 83: Zstd perf.data compression/decompression: ... util/session.c:1959:13: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 13 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ util/session.c:2163:22: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 8 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ ...Since there is no way to align compressed data in zstd compression, this patch add a new event type
PERF_RECORD_COMPRESSED2, which adds a fielddata_sizeto specify the actual compressed data size. Theheader.sizecontains the total record size, including the padding at the end to make it 8-byte aligned.Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Tested with
Zstd perf.data compression/decompressionLooks good to me.
Arnaldo, are you ok with adding a new record type for this?
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.Quoted 6 lines
Quoted 1 line
I'll try to reproduce/test this all...
I'm not sure we've worried about old perfs being able to read new perf.data files, but we've worried about new perfs being able to read old perf.data files. So if a change is additive, which this change is, then nothing should be impacted.
Right, its difficult to make it work both ways, even with testing, but by 'work' I mean that new stuff should be ignored by older versions, i.e. records skipped and then the results will surely be different.
So I'm just curious how older tools will handle these new files and to, if not that super difficult, to improve how we handle unknown records so that in the future, when we add new stuff, we mention that this is something not handled, please use a new tool.
Quoted 6 lines
My thoughts are this way as this patch:
https://lore.kernel.org/all/[email protected]/
changed most perf.data cpumap encodings in a way that old perfs won't be able to handle.Perhaps testing/documentation should be present for this kind of thing.
Quoted 7 lines
Right, but in this specific case it should be a matter of telling the user that the header.type
PERF_RECORD_COMPRESS2isn't supported and that the user should try and update their tool.But now back to figuring out how to generate
PERF_RECORD_COMPRESSis generated, use it, then apply this patch, and then see if how the old tool copes.
Which is present in this series, we have even a perf test shell for it, so happy to not having figured that before :-)
# Build with asan
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined" # Test success with many asan runtime errors: $ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv 83: Zstd perf.data compression/decompression:
Quoted 4 lines
So documentation is also lacking in suggesting that enumerating the steps needed to test before/after is greatly appreciated.
- Arnaldo
Namhyung Kim
maintainerQuoted 36 lines · Arnaldo Carvalho de Melo
Quoted 27 lines · Arnaldo Carvalho de Melo
Quoted 25 lines · Namhyung Kim
Quoted 24 lines · Chun-Tse Shao
The original
PERF_RECORD_COMPRESSis not 8-byte aligned, which can cause asan runtime error:# Build with asan
$ make -C tools/perf O=/tmp/perf DEBUG=1 EXTRA_CFLAGS="-O0 -g -fno-omit-frame-pointer -fsanitize=undefined" # Test success with many asan runtime errors: $ /tmp/perf/perf test "Zstd perf.data compression/decompression" -vv 83: Zstd perf.data compression/decompression: ... util/session.c:1959:13: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 13 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ util/session.c:2163:22: runtime error: member access within misaligned address 0x7f69e3f99653 for type 'union perf_event', which requires 8 byte alignment 0x7f69e3f99653: note: pointer points here d0 3a 50 69 44 00 00 00 00 00 08 00 bb 07 00 00 00 00 00 00 44 00 00 00 00 00 00 00 ff 07 00 00 ^ ...Since there is no way to align compressed data in zstd compression, this patch add a new event type
PERF_RECORD_COMPRESSED2, which adds a fielddata_sizeto specify the actual compressed data size. Theheader.sizecontains the total record size, including the padding at the end to make it 8-byte aligned.Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Tested with
Zstd perf.data compression/decompressionLooks good to me.
Arnaldo, are you ok with adding a new record type for this?
Checking the discussion and the patch.
Quoted 7 lines
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.
I think it'll show the below warning:
<offset> [<size>]: failed to process type: 83
Thanks,
Namhyung
Arnaldo Carvalho de Melo
maintainerQuoted 9 lines · Namhyung Kim
Quoted 8 lines · Arnaldo Carvalho de Melo
Quoted 1 line · Arnaldo Carvalho de Melo
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?
Quoted 6 lines
Quoted 2 lines
Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.I think it'll show the below warning:
<offset> [<size>]: failed to process type: 83
Right that is what I got:
⬢ [acme@toolbox perf-tools-next]$ perf.old script -i /tmp/perf.data.ck8 0xbf0 [0x250]: failed to process type: 83 [Invalid argument] ⬢ [acme@toolbox perf-tools-next]$
I think we should change that to something more informative, like:
0xbf0 [0x250]: failed to process unknown type 83, please update perf.
And then does it stop at that record it doesn't grok?
if ((skip = perf_session__process_event(session, event, head, "pipe")) < 0) {
pr_err("%#" PRIx64 " [%#x]: failed to process type: %d\n",
head, event->header.size, event->header.type);
err = -EINVAL;
goto out_err;
}
head += size;So we're stopping there.
Maybe we can just warn and skip?
Anyway, the series as is seems ok.
I'll test a bit more and send my Tested-by
- Arnaldo
Quoted 39 lines · Arnaldo Carvalho de Melo
Quoted 9 lines · Namhyung Kim
Quoted 8 lines · Arnaldo Carvalho de Melo
Quoted 1 line · Arnaldo Carvalho de Melo
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?Quoted 6 lines
Quoted 2 lines
Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.I think it'll show the below warning:
<offset> [<size>]: failed to process type: 83
Right that is what I got:
⬢ [acme@toolbox perf-tools-next]$ perf.old script -i
/tmp/perf.data.ck80xbf0[0x250]: failed to process type: 83 [Invalid argument] ⬢ [acme@toolbox perf-tools-next]$I think we should change that to something more informative, like:
0xbf0[0x250]: failed to process unknown type 83, please update perf.And then does it stop at that record it doesn't grok?
if ((skip = perf_session__process_event(session, event, head, "pipe")) < 0) { pr_err("%#" PRIx64 " [%#x]: failed to process type: %d\n", head, event->header.size, event->header.type); err = -EINVAL; goto out_err; } head += size;
Quoted 3 lines
So we're stopping there.
Maybe we can just warn and skip?
Thank you Arnaldo, it is a good suggestion and I will work on this later.
-CT
Quoted 6 lines
Anyway, the series as is seems ok.
I'll test a bit more and send my Tested-by
- Arnaldo
Arnaldo Carvalho de Melo
maintainerQuoted 39 lines · Chun-Tse Shao
Quoted 37 lines · Arnaldo Carvalho de Melo
Quoted 9 lines · Namhyung Kim
Quoted 8 lines · Arnaldo Carvalho de Melo
Quoted 1 line · Arnaldo Carvalho de Melo
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?Quoted 6 lines
Quoted 2 lines
Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.I think it'll show the below warning:
<offset> [<size>]: failed to process type: 83
Right that is what I got:
⬢ [acme@toolbox perf-tools-next]$ perf.old script -i
/tmp/perf.data.ck80xbf0[0x250]: failed to process type: 83 [Invalid argument] ⬢ [acme@toolbox perf-tools-next]$I think we should change that to something more informative, like:
0xbf0[0x250]: failed to process unknown type 83, please update perf.And then does it stop at that record it doesn't grok?
if ((skip = perf_session__process_event(session, event, head, "pipe")) < 0) { pr_err("%#" PRIx64 " [%#x]: failed to process type: %d\n", head, event->header.size, event->header.type); err = -EINVAL; goto out_err; }
Quoted 7 lines
Quoted 5 lines
head += size;So we're stopping there.
Maybe we can just warn and skip?
Thank you Arnaldo, it is a good suggestion and I will work on this later.
Thank you for considering that, really appreciated!
perf deals with so much stuff and code flux that all the help that we can get is what is needed for it to continue to be relevant and useful.
After all what is the point of a tool that produces bad results? :-)
- Arnaldo
Quoted 8 lines
-CT
Quoted 6 lines
Anyway, the series as is seems ok.
I'll test a bit more and send my Tested-by
- Arnaldo
Namhyung Kim
maintainerHello,
Quoted 23 lines · Arnaldo Carvalho de Melo
Quoted 22 lines · Chun-Tse Shao
Quoted 20 lines · Arnaldo Carvalho de Melo
Quoted 9 lines · Namhyung Kim
Quoted 8 lines · Arnaldo Carvalho de Melo
Quoted 1 line · Arnaldo Carvalho de Melo
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?Quoted 6 lines
Quoted 2 lines
Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.I think it'll show the below warning:
<offset> [<size>]: failed to process type: 83
Right that is what I got:
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
⬢ [acme@toolbox perf-tools-next]$ perf.old script -i
/tmp/perf.data.ck80xbf0[0x250]: failed to process type: 83 [Invalid argument] ⬢ [acme@toolbox perf-tools-next]$I think we should change that to something more informative, like:
0xbf0[0x250]: failed to process unknown type 83, please update perf.
That would be nice, but there are cases it can fail even without new record formats. So it should also check if the type number is greater than or equal to the max.
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
And then does it stop at that record it doesn't grok?
if ((skip = perf_session__process_event(session, event, head, "pipe")) < 0) { pr_err("%#" PRIx64 " [%#x]: failed to process type: %d\n", head, event->header.size, event->header.type); err = -EINVAL; goto out_err; } head += size;
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
So we're stopping there.
Maybe we can just warn and skip?
Thank you Arnaldo, it is a good suggestion and I will work on this later.
Thank you for considering that, really appreciated!
It would be hard to process misaligned data though. Probably we also want to add a check to make sure it's properly aligned.
Thanks,
Namhyung
Quoted 16 lines
perf deals with so much stuff and code flux that all the help that we can get is what is needed for it to continue to be relevant and useful.
After all what is the point of a tool that produces bad results? :-)
- Arnaldo
Quoted 8 lines
-CT
Quoted 6 lines
Anyway, the series as is seems ok.
I'll test a bit more and send my Tested-by
- Arnaldo
Ping.
For suggestions from Namhyung and Arnaldo, it was merged in:
Thanks,
CT
Quoted 81 lines · Namhyung Kim
Hello,
Quoted 23 lines · Arnaldo Carvalho de Melo
Quoted 22 lines · Chun-Tse Shao
Quoted 20 lines · Arnaldo Carvalho de Melo
Quoted 9 lines · Namhyung Kim
Quoted 8 lines · Arnaldo Carvalho de Melo
Quoted 1 line · Arnaldo Carvalho de Melo
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?Quoted 6 lines
Quoted 2 lines
Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.I think it'll show the below warning:
<offset> [<size>]: failed to process type: 83
Right that is what I got:
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
⬢ [acme@toolbox perf-tools-next]$ perf.old script -i
/tmp/perf.data.ck80xbf0[0x250]: failed to process type: 83 [Invalid argument] ⬢ [acme@toolbox perf-tools-next]$I think we should change that to something more informative, like:
0xbf0[0x250]: failed to process unknown type 83, please update perf.That would be nice, but there are cases it can fail even without new record formats. So it should also check if the type number is greater than or equal to the max.
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
And then does it stop at that record it doesn't grok?
if ((skip = perf_session__process_event(session, event, head, "pipe")) < 0) { pr_err("%#" PRIx64 " [%#x]: failed to process type: %d\n", head, event->header.size, event->header.type); err = -EINVAL; goto out_err; } head += size;Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
So we're stopping there.
Maybe we can just warn and skip?
Thank you Arnaldo, it is a good suggestion and I will work on this later.
Thank you for considering that, really appreciated!
It would be hard to process misaligned data though. Probably we also want to add a check to make sure it's properly aligned.
Thanks,
NamhyungQuoted 16 lines
perf deals with so much stuff and code flux that all the help that we can get is what is needed for it to continue to be relevant and useful.
After all what is the point of a tool that produces bad results? :-)
- Arnaldo
Quoted 8 lines
-CT
Quoted 6 lines
Anyway, the series as is seems ok.
I'll test a bit more and send my Tested-by
- Arnaldo
Arnaldo Carvalho de Melo
maintainerQuoted 5 lines · Chun-Tse Shao
Ping.
For suggestions from Namhyung and Arnaldo, it was merged in:
Testing it now, fixed up this:
+It is deprecated and new files should use PERF_RECORD_COMPRESSED2 to gurantee
guarantee
+8-byte alignment.
- Arnaldo
Quoted 85 lines
Thanks,
CTQuoted 81 lines · Namhyung Kim
Hello,
Quoted 23 lines · Arnaldo Carvalho de Melo
Quoted 22 lines · Chun-Tse Shao
Quoted 20 lines · Arnaldo Carvalho de Melo
Quoted 9 lines · Namhyung Kim
Quoted 8 lines · Arnaldo Carvalho de Melo
Quoted 1 line · Arnaldo Carvalho de Melo
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?Quoted 6 lines
Quoted 2 lines
Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.I think it'll show the below warning:
<offset> [<size>]: failed to process type: 83
Right that is what I got:
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
⬢ [acme@toolbox perf-tools-next]$ perf.old script -i
/tmp/perf.data.ck80xbf0[0x250]: failed to process type: 83 [Invalid argument] ⬢ [acme@toolbox perf-tools-next]$I think we should change that to something more informative, like:
0xbf0[0x250]: failed to process unknown type 83, please update perf.That would be nice, but there are cases it can fail even without new record formats. So it should also check if the type number is greater than or equal to the max.
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
And then does it stop at that record it doesn't grok?
if ((skip = perf_session__process_event(session, event, head, "pipe")) < 0) { pr_err("%#" PRIx64 " [%#x]: failed to process type: %d\n", head, event->header.size, event->header.type); err = -EINVAL; goto out_err; } head += size;Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
So we're stopping there.
Maybe we can just warn and skip?
Thank you Arnaldo, it is a good suggestion and I will work on this later.
Thank you for considering that, really appreciated!
It would be hard to process misaligned data though. Probably we also want to add a check to make sure it's properly aligned.
Thanks,
NamhyungQuoted 16 lines
perf deals with so much stuff and code flux that all the help that we can get is what is needed for it to continue to be relevant and useful.
After all what is the point of a tool that produces bad results? :-)
- Arnaldo
Quoted 8 lines
-CT
Quoted 6 lines
Anyway, the series as is seems ok.
I'll test a bit more and send my Tested-by
- Arnaldo
Thank you for the fix, Arnaldo!
-CT
Quoted 101 lines · Arnaldo Carvalho de Melo
Quoted 5 lines · Chun-Tse Shao
Ping.
For suggestions from Namhyung and Arnaldo, it was merged in:
Testing it now, fixed up this:
+It is deprecated and new files should use
PERF_RECORD_COMPRESSED2to gurantee
guarantee
+8-byte alignment.- Arnaldo
Quoted 85 lines
Thanks,
CTQuoted 81 lines · Namhyung Kim
Hello,
Quoted 23 lines · Arnaldo Carvalho de Melo
Quoted 22 lines · Chun-Tse Shao
Quoted 20 lines · Arnaldo Carvalho de Melo
Quoted 9 lines · Namhyung Kim
Quoted 8 lines · Arnaldo Carvalho de Melo
Quoted 1 line · Arnaldo Carvalho de Melo
Checking the discussion and the patch.
My first impression yesterday when I saw this on the smartphone was: how will an old perf binary handle the new
PERF_RECORD_COMPRESSED2? Will it ignore it while emitting a warning, since it can be skipped and then what we will get a partial view?Quoted 6 lines
Quoted 2 lines
Having some session output showing how an older perf binary handles
PERF_RECORD_COMPRESS2would be informative.I think it'll show the below warning:
<offset> [<size>]: failed to process type: 83
Right that is what I got:
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
⬢ [acme@toolbox perf-tools-next]$ perf.old script -i
/tmp/perf.data.ck80xbf0[0x250]: failed to process type: 83 [Invalid argument] ⬢ [acme@toolbox perf-tools-next]$I think we should change that to something more informative, like:
0xbf0[0x250]: failed to process unknown type 83, please update perf.That would be nice, but there are cases it can fail even without new record formats. So it should also check if the type number is greater than or equal to the max.
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
And then does it stop at that record it doesn't grok?
if ((skip = perf_session__process_event(session, event, head, "pipe")) < 0) { pr_err("%#" PRIx64 " [%#x]: failed to process type: %d\n", head, event->header.size, event->header.type); err = -EINVAL; goto out_err; } head += size;Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
So we're stopping there.
Maybe we can just warn and skip?
Thank you Arnaldo, it is a good suggestion and I will work on this later.
Thank you for considering that, really appreciated!
It would be hard to process misaligned data though. Probably we also want to add a check to make sure it's properly aligned.
Thanks,
NamhyungQuoted 16 lines
perf deals with so much stuff and code flux that all the help that we can get is what is needed for it to continue to be relevant and useful.
After all what is the point of a tool that produces bad results? :-)
- Arnaldo
Quoted 8 lines
-CT
Quoted 6 lines
Anyway, the series as is seems ok.
I'll test a bit more and send my Tested-by
- Arnaldo