From: Leo Yan <leo.yan@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
James Clark <james.clark@linaro.org>,
Mike Leach <mike.leach@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
Tamas Zsoldos <tamas.zsoldos@arm.com>
Subject: Re: [PATCH] coresight: trbe: Use scope-based resource management in arm_trbe_alloc_buffer()
Date: Fri, 12 Sep 2025 11:27:43 +0100 [thread overview]
Message-ID: <20250912102743.GG12516@e132581.arm.com> (raw)
In-Reply-To: <3f2137d5-5bfc-44e7-9269-3069e44eda31@arm.com>
On Fri, Sep 12, 2025 at 09:55:57AM +0530, Anshuman Khandual wrote:
[...]
> Seems like a good idea though. But please keep the local variable
> declaration in the current place which is bit cleaner and reduces
> code churn as well.
Though include/linux/cleanup.h suggests to "always define and assign
variables in one statement" to avoid potential interdependency problem
with lock, this is not concerned in arm_trbe_alloc_buffer().
So I bias to Anshuman's suggestion of declaring variables at the top
of the function, as this is the style widely used in the kernel.
> diff --git a/drivers/hwtracing/coresight/coresight-trbe.c b/drivers/hwtracing/coresight/coresight-trbe.c
> index 7a226316c48f..7babba1a9afb 100644
> --- a/drivers/hwtracing/coresight/coresight-trbe.c
> +++ b/drivers/hwtracing/coresight/coresight-trbe.c
> @@ -733,8 +733,8 @@ static void *arm_trbe_alloc_buffer(struct coresight_device *csdev,
> struct perf_event *event, void **pages,
> int nr_pages, bool snapshot)
> {
> - struct trbe_buf *buf;
> - struct page **pglist;
> + struct trbe_buf *buf __free(kfree);
struct trbe_buf *buf __free(kfree) = NULL;
> + struct page **pglist __free(kfree);
struct page **pglist __free(kfree) = NULL;
> int i;
>
> /*
> @@ -751,27 +751,22 @@ static void *arm_trbe_alloc_buffer(struct coresight_device *csdev,
> return NULL;
>
> pglist = kcalloc(nr_pages, sizeof(*pglist), GFP_KERNEL);
> - if (!pglist) {
> - kfree(buf);
> + if (!pglist)
> return NULL;
> - }
>
> for (i = 0; i < nr_pages; i++)
> pglist[i] = virt_to_page(pages[i]);
>
> buf->trbe_base = (unsigned long)vmap(pglist, nr_pages, VM_MAP, PAGE_KERNEL);
> - if (!buf->trbe_base) {
> - kfree(pglist);
> - kfree(buf);
> + if (!buf->trbe_base)
> return NULL;
> - }
> +
> buf->trbe_limit = buf->trbe_base + nr_pages * PAGE_SIZE;
> buf->trbe_write = buf->trbe_base;
> buf->snapshot = snapshot;
> buf->nr_pages = nr_pages;
> buf->pages = pages;
> - kfree(pglist);
> - return buf;
> + return_ptr(buf);
> }
>
> static void arm_trbe_free_buffer(void *config)
next prev parent reply other threads:[~2025-09-12 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 12:28 Markus Elfring
2025-09-12 4:25 ` Anshuman Khandual
2025-09-12 6:00 ` Markus Elfring
2025-09-12 10:27 ` Leo Yan [this message]
2025-09-12 12:37 ` Markus Elfring
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=20250912102743.GG12516@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=Markus.Elfring@web.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=tamas.zsoldos@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®