trace: Update the file header

It seems better to put the TEXT_BASE value in the file header rather than
in an entry record. While it is true that there is a separate base for
pre-relocation, this can be handled by using offsets in the file.

It is useful to have a version number in case we need to change the trace
format again.

Update the header to make these changes.

Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Simon Glass 2023-01-15 14:15:46 -07:00 committed by Tom Rini
parent 90ad4e28e8
commit d9044e5363
2 changed files with 14 additions and 17 deletions

View file

@ -6,6 +6,8 @@
#ifndef __TRACE_H
#define __TRACE_H
/* this file is included from a tool so uses uint32_t instead of u32, etc. */
enum {
/*
* This affects the granularity of our trace. We can bin function
@ -23,6 +25,8 @@ enum {
* this value.
*/
FUNC_SITE_SIZE = 4, /* distance between function sites */
TRACE_VERSION = 1,
};
enum trace_chunk_type {
@ -39,7 +43,11 @@ struct trace_output_func {
/* A header at the start of the trace output buffer */
struct trace_output_hdr {
enum trace_chunk_type type; /* Record type */
size_t rec_count; /* Number of records */
uint32_t version; /* Version (TRACE_VERSION) */
uint32_t rec_count; /* Number of records */
uint32_t spare; /* 0 */
uint64_t text_base; /* Value of CONFIG_TEXT_BASE */
uint64_t spare2; /* 0 */
};
/* Print statistics about traced function calls */
@ -63,7 +71,7 @@ int trace_list_functions(void *buff, size_t buff_size, size_t *needed);
enum ftrace_flags {
FUNCF_EXIT = 0UL << 30,
FUNCF_ENTRY = 1UL << 30,
FUNCF_TEXTBASE = 2UL << 30,
/* two more values are available */
FUNCF_TIMESTAMP_MASK = 0x3fffffff,
};