From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Leo Yan <leo.yan@arm.com>
Cc: Junhao He <hejunhao3@h-partners.com>,
james.clark@linaro.org, anshuman.khandual@arm.com,
yeoreum.yun@arm.com, mike.leach@linaro.org,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linuxarm@huawei.com,
jonathan.cameron@huawei.com
Subject: Re: [PATCH v4 2/3] coresight: tmc: refactor the tmc-etr mode setting to avoid race conditions
Date: Thu, 20 Nov 2025 10:45:04 +0000 [thread overview]
Message-ID: <cdbd12fb-af91-4e22-ab19-4018bc88f6c7@arm.com> (raw)
In-Reply-To: <20251119180447.GG8204@e132581.arm.com>
On 19/11/2025 18:04, Leo Yan wrote:
> On Thu, Nov 13, 2025 at 03:02:45PM +0000, Suzuki Kuruppassery Poulose wrote:
>> Hi Junhao,
>>
>> While your patch fixes the problem it introduces imbalance in the
>> way perf vs sysfs modes are handled.
>
> Previously, I suggested setting the mode in a unified way in
> tmc_enable_etr_sink() [1]. After looking into the code again, it seems
> that both my suggestion and this patch set the perf mode is too late.
>
> Maybe we need to set the sink's device mode once a session starts to use
> it. So we should set the perf mode when allocating sink's buffer
> (tmc_alloc_etr_buffer()), as this is the first callback invoked for a
> perf session.
Thats too early, in setup_aux(), when the event is not scheduled in. We
don't know when that would be.
>
> As a result, we can keep to set the sysfs mode in
> tmc_enable_etr_sink_sysfs().
>
> A side topic is we need to refactor the tmc_etr_get_sysfs_buffer()
> function, ideally this function is purely for allocating buffer without
> any locking. We can defer to assign "drvdata->sysfs_buf" until
> acquired spin lock in tmc_enable_etr_sink_sysfs(). Essetionally, we
> can enable sink in one go rather than acquire-release lock for several
> times.
Patche welcome :-)
Cheers
Suzuki
>
> Thanks,
> Leo
>
> [1] https://lore.kernel.org/linux-arm-kernel/20251020143718.GH281971@e132581.arm.com/
next prev parent reply other threads:[~2025-11-20 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 12:21 [PATCH v4 0/3] Coresight TMC-ETR: refactor the tmc-etr mode and some cleanups Junhao He
2025-11-11 12:21 ` [PATCH v4 1/3] coresight: tmc: Add missing doc including reading and etr_mode of struct tmc_drvdata Junhao He
2025-11-11 12:21 ` [PATCH v4 2/3] coresight: tmc: refactor the tmc-etr mode setting to avoid race conditions Junhao He
2025-11-13 15:02 ` Suzuki K Poulose
[not found] ` <14a564bf-f9a2-c49c-9cd6-a5b68bc43500@h-partners.com>
2025-11-19 14:46 ` Suzuki K Poulose
2025-12-29 8:27 ` hejunhao
2025-11-19 18:04 ` Leo Yan
2025-11-20 10:45 ` Suzuki K Poulose [this message]
2025-11-11 12:21 ` [PATCH v4 3/3] coresight: tmc: Decouple the perf buffer allocation from sysfs mode Junhao He
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=cdbd12fb-af91-4e22-ab19-4018bc88f6c7@arm.com \
--to=suzuki.poulose@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=hejunhao3@h-partners.com \
--cc=james.clark@linaro.org \
--cc=jonathan.cameron@huawei.com \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mike.leach@linaro.org \
--cc=yeoreum.yun@arm.com \
/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®