[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <71158b94-863d-97d3-323a-e2406b708db7@arm.com>
Date: Thu, 10 Jun 2021 17:54:20 +0300
From: James Clark <james.clark@....com>
To: Leo Yan <leo.yan@...aro.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Suzuki K Poulose <suzuki.poulose@....com>,
Mike Leach <mike.leach@...aro.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
John Garry <john.garry@...wei.com>,
Will Deacon <will@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Daniel Kiss <daniel.kiss@....com>,
Denis Nikitin <denik@...gle.com>, coresight@...ts.linaro.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH v1 1/3] coresight: etm-perf: Correct buffer syncing for
snapshot
On 01/06/2021 13:35, Leo Yan wrote:
> Hi James,
>
> On Tue, Jun 01, 2021 at 12:53:16PM +0300, James Clark wrote:
>
> [...]
>
>> Hi Leo,
>>
>> I was testing out snapshot mode (without your patch) and I noticed that it
>> only ever collects from the last CPU. For example on a 4 core system,
>> the CPU ID of the AUX records and the AUXTRACE buffers is always 3.
>>
>> This is with systemwide tracing, and running "stress -m 2 -c 2".
>> Is this something that your patch fixes, or am I doing something wrong, or
>> is it just a coincidence?
>
> No, I think it's quite likely caused by blow code:
>
> static unsigned long
> tmc_update_etr_buffer(struct coresight_device *csdev,
> struct perf_output_handle *handle,
> void *config)
> {
> unsigned long flags, offset, size = 0;
>
> ...
>
> /* Don't do anything if another tracer is using this sink */
> if (atomic_read(csdev->refcnt) != 1) {
> spin_unlock_irqrestore(&drvdata->spinlock, flags);
> goto out;
> }
>
> ...
>
> return size;
> }
>
> When using the system wide tracing, it updates the AUX ring buffer
> until the last tracer is stopped. Thus whis is why it only records
> AUX ring buffer for the last CPU.
>
> But this makes sense for me, this is because the last CPU is used to
> copy trace data to AUX ring buffer (so the perf event PERF_RECORD_AUX
> occurs on CPU3), but when you decode the trace data, you should can
> see the activities from other CPUs.
>
> Thanks,
> Leo
>
I have one more issue around snapshot mode which I'd like to check if it's
related to this patchset.
In "[PATCH v5 0/1] perf cs-etm: Split Coresight decode by aux records",
I added the warning for a missing AUXTRACE buffer as you suggested.
Now this warning gets triggered on the last AUX record when using
snapshot mode. I don't know if you are able to reproduce this.
Thanks
James
Powered by blists - more mailing lists