Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ftrace: fix trace entry size computation when header len is 0
In a trace.dat files, trace entries have a 32 bit header that contains the payload len (in 32 bit words) in the lower 5 bits. A len of 0 is a special case: the actual entry length is in the next 32 bit word, and that length includes the length field itself, so: - the event data starts after the length fields - the event data is len_in_next_word - 4 For documentation see: https://elixir.bootlin.com/linux/latest/source/include/linux/ring_buffer.h#L51 Change-Id: I91a459deb11c63f606406b6a1dac9b2b4fcf9130 Signed-off-by: Fabrizio Iannetti <fabrizio.iannetti@gmail.com> Reviewed-on: https://git.eclipse.org/r/c/tracecompass.incubator/org.eclipse.tracecompass.incubator/+/197834 Tested-by: Trace Compass Bot <tracecompass-bot@eclipse.org> Tested-by: Bernd Hufmann <bernd.hufmann@ericsson.com> Reviewed-by: Hoang Thuan Pham <hoangpham.eclipse@gmail.com> Reviewed-by: Bernd Hufmann <bernd.hufmann@ericsson.com>
- Loading branch information