From: James Clark <james.clark@linaro.org>
To: Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@arm.com>
Cc: Kuan-Wei Chiu <visitorckw@gmail.com>,
suzuki.poulose@arm.com, alexander.shishkin@linux.intel.com,
pratikp@codeaurora.org, mathieu.poirier@linaro.org,
gregkh@linuxfoundation.org, jserv@ccns.ncku.edu.tw,
marscheng@google.com, ericchancf@google.com,
milesjiang@google.com, nickpan@google.com,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coresight: etm3x: Fix buffer overwrite in cntr_val_show()
Date: Wed, 26 Nov 2025 15:33:22 +0000 [thread overview]
Message-ID: <15d536f2-0829-4f3f-b111-b15b14236bd2@linaro.org> (raw)
In-Reply-To: <CAJ9a7VhD2p3qMGXNg6deYjE8myB5euHR4FcAFwgg0KWF2HO9JQ@mail.gmail.com>
On 26/11/2025 1:42 pm, Mike Leach wrote:
> Hi,
>
> On Wed, 26 Nov 2025 at 12:31, Leo Yan <leo.yan@arm.com> wrote:
>>
>> On Wed, Nov 26, 2025 at 12:11:05PM +0000, James Clark wrote:
>>
>> [...]
>>
>>>> This fix can still be applied to older kernels, but seems to me that
>>>> now might be an appropriate time to consider removing the ETMv3 driver
>>>> from the mainline kernel?
>>>
>>> Yeah, if anyone is using it it would be on an old kernel surely?
>>
>> We can confirm this in another way: if I don't miss anything, over the
>> past several years (since 2017), we have not received any questions or
>> bug reports based on hands-on practice regarding ETMv3 on the Coresight
>> or perf mailing lists.
>>
>> Thanks,
>> Leo
>
> The key to this is not the questions we are asked, but which platforms
> are still supported by the linux kernel.
>
> The ETMv3 driver supports both ETMv3 and PTM trace (the programming
> model is the same, even if the trace decode is vastly different).
>
> So as long as there are platforms supported that use either of those,
> we need to keep the driver in.
>
> Mike
>
We're not running tests though, so if we find out it's fundamentally
broken somehow it could be another justification to remove it, even if
the kernel supports the devices. Do you have a board that you can test
on Mike?
Maintenance hasn't been zero cost either, even build testing for arm32
is annoying enough.
next prev parent reply other threads:[~2025-11-26 15:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 0:23 Kuan-Wei Chiu
2025-11-21 9:50 ` James Clark
2025-11-21 17:02 ` Kuan-Wei Chiu
2025-11-24 16:12 ` James Clark
2025-11-26 10:49 ` Mike Leach
2025-11-26 10:57 ` James Clark
2025-11-27 8:44 ` Kuan-Wei Chiu
2025-11-27 9:17 ` James Clark
2025-11-27 9:22 ` Leo Yan
2025-11-27 9:30 ` James Clark
2025-11-27 9:57 ` Leo Yan
2025-11-27 14:30 ` Mike Leach
2025-11-26 12:09 ` Leo Yan
2025-11-26 12:11 ` James Clark
2025-11-26 12:31 ` Leo Yan
2025-11-26 13:42 ` Mike Leach
2025-11-26 15:33 ` James Clark [this message]
2025-11-26 16:14 ` Mike Leach
2025-11-27 9:29 ` Leo Yan
2025-11-28 14:53 ` James Clark
2025-11-28 15:14 ` Al Grant
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=15d536f2-0829-4f3f-b111-b15b14236bd2@linaro.org \
--to=james.clark@linaro.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=ericchancf@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jserv@ccns.ncku.edu.tw \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marscheng@google.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=milesjiang@google.com \
--cc=nickpan@google.com \
--cc=pratikp@codeaurora.org \
--cc=suzuki.poulose@arm.com \
--cc=visitorckw@gmail.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®