CoreSight September 2026

coresight@lists.linaro.org

1 participants
11 discussions

Re: [PATCH] coresight: tpdm: initialize spinlock before exposing sysfs

by Leo Yan

On Tue, Aug 25, 2026 at 10:06:47AM +0800, yingchao wrote: > From: Yingchao Deng <dengyingchao(a)kylinsec.com.cn> > > tpdm_probe() initializes drvdata->spinlock after coresight_register(), but > the sysfs attributes registered by coresight_register() use the spinlock. > This exposes a window where a concurrent sysfs write can lock an > uninitialized spinlock. > > Initialize the spinlock before coresight_register(). > > Fixes: b3c71626a933 ("Coresight: Add coresight TPDM source driver") > Signed-off-by: Yingchao Deng <dengyingchao(a)kylinsec.com.cn> Reviewed-by: Leo Yan <leo.yan(a)arm.com>

8 hours, 44 minutes

Re: [PATCH] coresight: syscfg: fix deadlock on device registration failure

by Leo Yan

On Tue, Aug 25, 2026 at 09:47:17AM +0800, yingchao wrote: > diff --git a/drivers/hwtracing/coresight/coresight-syscfg.c b/drivers/hwtracing/coresight/coresight-syscfg.c > index 2bfdd7b45e49..d0e7e4720e46 100644 > --- a/drivers/hwtracing/coresight/coresight-syscfg.c > +++ b/drivers/hwtracing/coresight/coresight-syscfg.c > @@ -1210,8 +1210,14 @@ static int cscfg_create_device(void) > dev->init_name = "cs_system_cfg"; > > err = device_register(dev); > - if (err) > + if (err) { > + /* put_device() triggers cscfg_dev_release() which takes > + * cscfg_mutex, so drop the lock first to avoid deadlocking. > + */ > + mutex_unlock(&cscfg_mutex); > put_device(dev); > + return err; > + } As module init and exit are serialized by the kernel, I don't think we need the mutex to protect the allocation and freeing of cscfg_mgr. The mutex should only be used for exclusively access cscfg_mgr. So how about the change below? ---8<--- diff --git a/drivers/hwtracing/coresight/coresight-syscfg.c b/drivers/hwtracing/coresight/coresight-syscfg.c index 2bfdd7b45e49..2dd0b29f44e4 100644 --- a/drivers/hwtracing/coresight/coresight-syscfg.c +++ b/drivers/hwtracing/coresight/coresight-syscfg.c @@ -1173,27 +1173,21 @@ struct device *cscfg_device(void) /* Must have a release function or the kernel will complain on module unload */ static void cscfg_dev_release(struct device *dev) { - mutex_lock(&cscfg_mutex); kfree(cscfg_mgr); cscfg_mgr = NULL; - mutex_unlock(&cscfg_mutex); } /* a device is needed to "own" some kernel elements such as sysfs entries. */ static int cscfg_create_device(void) { struct device *dev; - int err = -ENOMEM; - - mutex_lock(&cscfg_mutex); - if (cscfg_mgr) { - err = -EINVAL; - goto create_dev_exit_unlock; - } + int err; cscfg_mgr = kzalloc_obj(struct cscfg_manager); if (!cscfg_mgr) - goto create_dev_exit_unlock; + return -ENOMEM; + + mutex_lock(&cscfg_mutex); /* initialise the cscfg_mgr structure */ INIT_LIST_HEAD(&cscfg_mgr->csdev_desc_list); @@ -1204,6 +1198,8 @@ static int cscfg_create_device(void) cscfg_mgr->load_state = CSCFG_NONE; raw_spin_lock_init(&cscfg_mgr->sysfs_store_lock); + mutex_unlock(&cscfg_mutex); + /* setup the device */ dev = cscfg_device(); dev->release = cscfg_dev_release; @@ -1213,8 +1209,6 @@ static int cscfg_create_device(void) if (err) put_device(dev); -create_dev_exit_unlock: - mutex_unlock(&cscfg_mutex); return err; }

8 hours, 46 minutes

[PATCH 0/6] perf: cs-etm: HW_ID improvements

by James Clark

The driver might not always be able to write HW_IDs, but we don't need them for unformatted mode anyway, so fix that in commit ("perf cs-etm: Synthesize missing HW_ID mappings for raw trace"). At the same time, give the driver another chance to send them in commit ("coresight: perf: Retry failed HW_ID writes"). The other commits are semi-related improvements and fixes. ("perf: cs-etm: Respect --no-itrace option") makes debugging broken Coresight perf.data files easier. Applies on top of "[PATCH v2 00/14] perf cs-etm: Per-thread mode fixes and snapshot wrap support" Signed-off-by: James Clark <james.clark(a)linaro.org> --- James Clark (5): perf: cs-etm: Don't add global v0 HW_IDs to unformatted queues perf cs-etm: Free partially created queues perf: cs-etm: Respect --no-itrace option perf/core: Return errors from perf_report_aux_output_id() coresight: perf: Retry failed HW_ID writes Leo Yan (1): perf cs-etm: Synthesize missing HW_ID mappings for raw trace drivers/hwtracing/coresight/coresight-etm-perf.c | 52 +++++---- include/linux/perf_event.h | 2 +- kernel/events/core.c | 6 +- tools/perf/util/auxtrace.c | 2 +- tools/perf/util/auxtrace.h | 1 + tools/perf/util/cs-etm.c | 143 ++++++++++++++++------- 6 files changed, 139 insertions(+), 67 deletions(-) --- base-commit: 78148c85297024ffe7a709acb7cc4fc907271176 change-id: 20260706-james-cs-hw_id-output-failure-1d06d042ef96 prerequisite-change-id: 20260605-james-cs-unformatted-per-thread-fix-50e723aa7f0e:v2 prerequisite-patch-id: 1aa32269a3a7dc76840dd8a24cb5a8715507e898 prerequisite-patch-id: ef471f468351462f67efa58a09a3461306ac5a0a prerequisite-patch-id: c78946cf4ec1c7722570865403a3562625bdaa33 prerequisite-patch-id: 0b953eee0252db3c7ba3ef1e3397048a94482ca2 prerequisite-patch-id: 27da72c2f01bcc68205bbcc14d5019369c02cb83 prerequisite-patch-id: 365c6d5f71c754e4c690b5ebed3453565bb5b809 prerequisite-patch-id: 64e9419a41082a2db3daf255baf0fb40efbae5dd prerequisite-patch-id: 1dc2e6ef8e76b369736b4c88560302861b2e4faf prerequisite-patch-id: b7de38ec4d90f5b45d56390a4e5919a1d6439951 prerequisite-patch-id: 3548d5b161cfb8c11a166ca2b3228ca4821f1ca0 prerequisite-patch-id: 97e66600218a2b32e5b21d0abcb6321590f98de9 prerequisite-patch-id: 292282b20bd8ad7d096ee7ffbc55dcfb75455f53 prerequisite-patch-id: c80259b47850ba65c985c85a29c8cf4948463d59 Best regards, -- James Clark <james.clark(a)linaro.org>

4 days, 7 hours

Re: [PATCH] coresight: fix typos in comments

by Leo Yan

On Fri, Sep 04, 2026 at 04:40:51PM +0530, Hemanth Selam wrote: > Fix typos in comments, reported by scripts/checkpatch.pl using the > misspelling list in scripts/spelling.txt. Only touches comments, no code > changes. > > Assisted-by: Cursor:claude-opus-5 > Signed-off-by: Hemanth Selam <hemanth.selam(a)gmail.com> Reviewed-by: Leo Yan <leo.yan(a)arm.com>

4 days, 11 hours

Re: [PATCH] docs: fix typos in Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x

by Leo Yan

On Fri, Sep 04, 2026 at 09:49:42AM +0530, tspamiitesh(a)gmail.com wrote: [...] > -Description: (RW) Enable/disable tracing on this specific trace entiry. > +Description: (RW) Enable/disable tracing on this specific trace entry. > Enabling a source implies the source has been configured > - properly and a sink has been identidifed for it. The path > + properly and a sink has been indentified for it. The path s/indentified/identified ?

4 days, 11 hours

Re: [PATCH v2] coresight: tnoc: fix trace ID path assignment failure on non-AMBA tnoc

by Leo Yan

On Wed, Sep 02, 2026 at 05:41:43PM +0800, Jie Gan wrote: > For a tnoc device not on the AMBA bus, atid was set to -EOPNOTSUPP. > trace_noc_id() returns this value directly to > coresight_path_assign_trace_id(), which only treats a literal 0 > return as "this device has no ID, keep searching the path" - > any other value is checked against IS_VALID_CS_TRACE_ID() and > rejected. A negative atid therefore made path assignment fail with > -EINVAL instead of falling through to the next device in the path > that could supply a valid trace ID. > > Use 0, the same sentinel coresight_path_assign_trace_id() already > recognizes as "not allocated", instead of -EOPNOTSUPP. > > Fixes: 5799dee92dc2 ("coresight-tnoc: add platform driver to support Interconnect TNOC") > Signed-off-by: Jie Gan <jie.gan(a)oss.qualcomm.com> Reviewed-by: Leo Yan <leo.yan(a)arm.com>

6 days, 15 hours

Re: [PATCH] coresight: fix trace ID search skipping pass-through NoC devices

by Leo Yan

On Wed, Sep 02, 2026 at 04:35:11PM +0800, Jie Gan wrote: [...] > Hi Leo, > > Thanks for the suggestion. You're welcome! > I will fix this in the TNOC driver. I agree that there is no need to use > additional error codes to report the failure. > > I will post the new fix patch after below patch[1] to be applied to avoid > conflict. The patch in the link has no fix tag, but current patch is a simple fix. I'd suggest to give priority this patch - this is friendly for porting to stable kernels. If there have dependency (based on your local test), you could explictly mention the dependency in cover letter and resend the tnoc probe series. Thanks, Leo > [1] https://lore.kernel.org/all/20260710-fix-tracenoc-probe-issue-v6-2-41eb36fe…

6 days, 16 hours

Re: [PATCH] coresight: fix trace ID search skipping pass-through NoC devices

by Leo Yan

Hi Jie, On Mon, Aug 17, 2026 at 04:50:15PM +0800, Jie Gan wrote: [...] > @@ -953,8 +953,12 @@ int coresight_path_assign_trace_id(struct coresight_path *path, > /* Assign a trace ID to the path for the first device that wants to do it */ > trace_id = coresight_get_trace_id(nd->csdev, mode, sink); > > - /* 0 means the device has no ID assignment, so keep searching */ > - if (trace_id == 0) > + /* > + * 0 means the device has no ID assignment, and -EOPNOTSUPP > + * means the device explicitly declines to assign one (e.g. a > + * pass-through NoC) - in both cases keep searching downstream. > + */ > + if (trace_id == 0 || trace_id == -EOPNOTSUPP) > continue; Based on IS_VALID_CS_TRACE_ID(), I see 0 is for no ID assignment, could you improve a bit tnoc.c instead? If so, We don't need to add a new error for the same purpose. ---8<--- diff --git a/drivers/hwtracing/coresight/coresight-tnoc.c b/drivers/hwtracing/coresight/coresight-tnoc.c index 9e8de4323d28..bf221c1e5c48 100644 --- a/drivers/hwtracing/coresight/coresight-tnoc.c +++ b/drivers/hwtracing/coresight/coresight-tnoc.c @@ -51,8 +51,8 @@ static void trace_noc_enable_hw(struct trace_noc_drvdata *drvdata) { u32 val; - /* No valid ATID, simply enable the unit */ - if (drvdata->atid == -EOPNOTSUPP) { + /* 0 means no ID assignment, simply enable the unit */ + if (!drvdata->atid) { writel(TRACE_NOC_CTRL_PORTEN, drvdata->base + TRACE_NOC_CTRL); return; } @@ -130,10 +130,8 @@ static int trace_noc_init_default_data(struct trace_noc_drvdata *drvdata) { int atid; - if (!dev_is_amba(drvdata->dev)) { - drvdata->atid = -EOPNOTSUPP; + if (!dev_is_amba(drvdata->dev)) return 0; - } atid = coresight_trace_id_get_system_id(); if (atid < 0)

6 days, 16 hours

Re: [PATCH 2/2] perf: arm_spe: Prefer large AUX mappings

by Leo Yan

On Mon, Aug 10, 2026 at 04:10:48PM +0100, Will Deacon wrote: > On Mon, Aug 10, 2026 at 03:44:42PM +0100, Leo Yan wrote: > > Commit 18049c8cff9c ("perf/aux: Allocate non-contiguous AUX pages by > > default") made the AUX allocator use order-0 pages by default unless a > > PMU explicitly asks for contiguous allocations. > > But that commit specifically calls out SPE as benefitting from > non-contiguous pages: > > "For instance, ARM SPE and TRBE operate with virtual pages, and > Coresight ETR allocates a separate buffer. For these PMUs, > allocating contiguous AUX pages unnecessarily exacerbates memory > fragmentation. This fragmentation can prevent their use on > long-running devices." > > so why doesn't passing PERF_PMU_CAP_AUX_PREFER_LARGE reintroduce the > problems that 18049c8cff9c was trying to solve? The question is how "allocating contiguous AUX pages unnecessarily exacerbates memory fragmentation." The relevant information I could find is [1]: "On Android, we collect ETM data periodically on internal user devices for AutoFDO optimization (for both userspace libraries and the kernel). Allocating a large chunk of contiguous AUX pages (4M for each CPU) periodically is almost unbearable. The kernel may need to kill many processes to fulfill the request. It affects user experience even after using PMU." We might have missed chance to clarify how the fragmentation issue occurs in the first place. Let's say, a phone with 8 CPUs, allocating 4MB per CPU requires 32MB in total, which is a relatively small portion of 4GiB or 8GiB of RAM commonly found in phones. Moreover, once contiguous pages are freed, the buddy allocator can coalesce them again into buddy list. It is not obvious to me that PREFER_LARGE directly causes fragmentation. One case where AUX allocation could exacerbate fragmentation is when the system is already fragmented. If a high-order allocation fails and the allocator falls back to smaller-order blocks, those allocations may consume free blocks scattered across different buddy regions and make subsequent high-order allocations more difficult. If this is the main concern, I'd suggest using a smaller AUX buffer (e.g. 1MB or even 512KB) for TRBE/SPE to reduce memory pressure. Snapshot mode '-S' could also be considered, as it allows the buffer to be allocated once and reused for subsequent recordings by signals. OTOH, using only order-0 pages can significantly increase TTW overhead on the trace path and lead to overflows, we observe this causes huge trace discontinuity. In the end, we need to trace-off the fragmentation concern against the trace discontinuity. Thanks, Leo [1] https://lore.kernel.org/lkml/CALJ9ZPNLgEBxOmDim-vztUknEETwdL-Z2gJ8K9s44TiPg…

1 week

Re: [PATCH v4] coresight: coresight.h: add '*' to kernel-doc lines

by Leo Yan

On Sun, Aug 30, 2026 at 08:09:12PM -0700, Randy Dunlap wrote: > kernel-doc reports 2 (kernel-doc) lines in coresight.h that don't have > a beginning '*' in them, so fix these lines. > > Also convert struct coresight_trace_id_map to kernel-doc format to > remove another warning. > > Warning: include/linux/coresight.h:173 bad line: > connected to @src_port. NULL until the device is created > Warning: include/linux/coresight.h:177 bad line: > needs to be filtered. > Warning: include/linux/coresight.h:236 This comment starts with '/**', > but isn't a kernel-doc comment. > > Fixes: ec9903d6cc34 ("coresight: Add support for trace filtering by source") > Fixes: d49c9cf15f89 ("coresight: Rename connection members to make the direction explicit") > Signed-off-by: Randy Dunlap <rdunlap(a)infradead.org> Reviewed-by: Leo Yan <leo.yan(a)arm.com>

1 week

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CoreSight September 2026