From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: James Clark <james.clark@arm.com>,
mathieu.poirier@linaro.org, coresight@lists.linaro.org
Cc: Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] coresight: Don't immediately close events that are run on invalid CPU/sink combos
Date: Wed, 22 Sep 2021 16:20:56 +0100 [thread overview]
Message-ID: <b36e8a19-4867-c788-7d68-774a3244fa61@arm.com> (raw)
In-Reply-To: <20210922125144.133872-2-james.clark@arm.com>
On 22/09/2021 13:51, James Clark wrote:
> When a traced process runs on a CPU that can't reach the selected sink,
> the event will be stopped with PERF_HES_STOPPED. This means that even if
> the process migrates to a valid CPU, tracing will not resume.
>
> This can be reproduced (on N1SDP) by using taskset to start the process
> on CPU 0, and then switching it to CPU 2 (ETF 1 is only reachable from
> CPU 2):
>
> taskset --cpu-list 0 ./perf record -e cs_etm/@tmc_etf1/ --per-thread -- taskset --cpu-list 2 ls
>
> This produces a single 0 length AUX record, and then no more trace:
>
> 0x3c8 [0x30]: PERF_RECORD_AUX offset: 0 size: 0 flags: 0x1 [T]
>
> After the fix, the same command produces normal AUX records. The perf
> self test "89: Check Arm CoreSight trace data recording and synthesized
> samples" no longer fails intermittently. This was because the taskset in
> the test is after the fork, so there is a period where the task is
> scheduled on a random CPU rather than forced to a valid one.
>
> Specifically selecting an invalid CPU will still result in a failure to
> open the event because it will never produce trace:
>
> ./perf record -C 2 -e cs_etm/@tmc_etf0/
> failed to mmap with 12 (Cannot allocate memory)
>
> The only scenario that has changed is if the CPU mask has a valid CPU
> sink combo in it.
>
> Testing
> =======
>
> * Coresight self test passes consistently:
> ./perf test Coresight
>
> * CPU wide mode still produces trace:
> ./perf record -e cs_etm// -a
>
> * Invalid -C options still fail to open:
> ./perf record -C 2,3 -e cs_etm/@tmc_etf0/
> failed to mmap with 12 (Cannot allocate memory)
>
> * Migrating a task to a valid sink/CPU now produces trace:
> taskset --cpu-list 0 ./perf record -e cs_etm/@tmc_etf1/ --per-thread -- taskset --cpu-list 2 ls
>
> * If the task remains on an invalid CPU, no trace is emitted:
> taskset --cpu-list 0 ./perf record -e cs_etm/@tmc_etf1/ --per-thread -- ls
>
> Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> Signed-off-by: James Clark <james.clark@arm.com>
Thanks James, I have queued this.
Suzuki
prev parent reply other threads:[~2021-09-22 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 12:51 [PATCH v2 0/1] " James Clark
2021-09-22 12:51 ` [PATCH v2 1/1] coresight: " James Clark
2021-09-22 15:20 ` Suzuki K Poulose [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b36e8a19-4867-c788-7d68-774a3244fa61@arm.com \
--to=suzuki.poulose@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®