[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210209095857.28419-4-james.clark@arm.com>
Date: Tue, 9 Feb 2021 11:58:55 +0200
From: James Clark <james.clark@....com>
To: coresight@...ts.linaro.org
Cc: al.grant@....com, branislav.rankov@....com, denik@...omium.org,
James Clark <james.clark@....com>,
Mike Leach <mike.leach@...aro.org>,
Leo Yan <leo.yan@...aro.org>,
John Garry <john.garry@...wei.com>,
Will Deacon <will@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: [RFC PATCH 3/5] perf cs-etm: Save aux records in each etm queue
The aux records will be used set the bounds of decoding in a
later commit. In the future we may also want to use the flags
of each record to control decoding.
Do these need to be saved in their entirety, or can pointers
to each record safely be saved instead for later access?
Signed-off-by: James Clark <james.clark@....com>
---
tools/perf/util/cs-etm.c | 24 +++++++++++++++++++-----
1 file changed, 19 insertions(+), 5 deletions(-)
diff --git a/tools/perf/util/cs-etm.c b/tools/perf/util/cs-etm.c
index 9ebe43d60d1e..efe418a7c82e 100644
--- a/tools/perf/util/cs-etm.c
+++ b/tools/perf/util/cs-etm.c
@@ -92,12 +92,16 @@ struct cs_etm_queue {
/* Conversion between traceID and index in traceid_queues array */
struct intlist *traceid_queues_list;
struct cs_etm_traceid_queue **traceid_queues;
+ int aux_record_list_len;
+ int aux_record_list_idx;
+ struct perf_record_aux *aux_record_list;
};
/* RB tree for quick conversion between traceID and metadata pointers */
static struct intlist *traceid_list;
-static int cs_etm__update_queues(struct cs_etm_auxtrace *etm, int cpu);
+static int cs_etm__update_queues(struct cs_etm_auxtrace *etm, int cpu,
+ struct perf_record_aux *aux_record);
static int cs_etm__process_queues(struct cs_etm_auxtrace *etm);
static int cs_etm__process_timeless_queues(struct cs_etm_auxtrace *etm,
pid_t tid);
@@ -593,6 +597,7 @@ static void cs_etm__free_queue(void *priv)
cs_etm_decoder__free(etmq->decoder);
cs_etm__free_traceid_queues(etmq);
+ free(etmq->aux_record_list);
free(etmq);
}
@@ -767,13 +772,22 @@ static struct cs_etm_queue *cs_etm__alloc_queue(struct cs_etm_auxtrace *etm)
return NULL;
}
-static int cs_etm__seach_first_timestamp(struct cs_etm_queue *etmq)
+static int cs_etm__seach_first_timestamp(struct cs_etm_queue *etmq,
+ struct perf_record_aux *aux_record)
{
int ret = 0;
u64 timestamp;
unsigned int cs_queue_nr;
u8 trace_chan_id;
+ etmq->aux_record_list = reallocarray(etmq->aux_record_list,
+ etmq->aux_record_list_len+1,
+ sizeof(*etmq->aux_record_list));
+ if (!etmq->aux_record_list)
+ return -ENOMEM;
+
+ etmq->aux_record_list[etmq->aux_record_list_len++] = *aux_record;
+
/*
* We are under a CPU-wide trace scenario. As such we need to know
* when the code that generated the traces started to execute so that
@@ -873,7 +887,7 @@ static int cs_etm__setup_queues(struct cs_etm_auxtrace *etm)
return 0;
}
-static int cs_etm__update_queues(struct cs_etm_auxtrace *etm, int cpu)
+static int cs_etm__update_queues(struct cs_etm_auxtrace *etm, int cpu, struct perf_record_aux *aux)
{
int ret;
if (etm->queues.new_data) {
@@ -884,7 +898,7 @@ static int cs_etm__update_queues(struct cs_etm_auxtrace *etm, int cpu)
}
if (!etm->timeless_decoding)
- return cs_etm__seach_first_timestamp(etm->queues.queue_array[cpu].priv);
+ return cs_etm__seach_first_timestamp(etm->queues.queue_array[cpu].priv, aux);
else
return 0;
}
@@ -2365,7 +2379,7 @@ static int cs_etm__process_event(struct perf_session *session,
if ((timestamp || etm->timeless_decoding)
&& event->header.type == PERF_RECORD_AUX) {
- err = cs_etm__update_queues(etm, sample->cpu);
+ err = cs_etm__update_queues(etm, sample->cpu, &event->aux);
if (err)
return err;
}
--
2.28.0
Powered by blists - more mailing lists