From: Markus Elfring <Markus.Elfring@web.de>
To: Sang-Heon Jeon <ekffu200098@gmail.com>,
cocci@inria.fr, Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [cocci] [PATCH 1/3] coccinelle: mini_lock: improve performance when searching loops
Date: Sun, 26 Jul 2026 15:55:33 +0200 [thread overview]
Message-ID: <c5a73800-59cd-4870-ae57-11fe832054b9@web.de> (raw)
In-Reply-To: <20260725113303.691676-2-ekffu200098@gmail.com>
…
> +++ b/scripts/coccinelle/locks/mini_lock.cocci
> @@ -53,11 +53,31 @@ spin_lock_irq@p1
> spin_lock_irqsave@p1
> ) (E1@p,...);
>
> -@looped@
> +@err_candidate exists@
> +expression E1;
> +position prelocked.p;
> +position up != prelocked.p1;
> +position rc;
…
Can it help a bit to avoid the repetition of the type
for a few metavariables?
+position prelocked.p, up != prelocked.p1, rc;
Regards,
Markus
next prev parent reply other threads:[~2026-07-26 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 11:32 [PATCH 0/3] coccinelle: improve performance of mini_lock, double_lock and minmax Sang-Heon Jeon
2026-07-25 11:32 ` [PATCH 1/3] coccinelle: mini_lock: improve performance when searching loops Sang-Heon Jeon
2026-07-26 13:55 ` Markus Elfring [this message]
2026-07-26 14:14 ` [cocci] " Julia Lawall
2026-07-26 16:42 ` Julia Lawall
2026-07-27 11:11 ` Sang-Heon Jeon
2026-07-25 11:32 ` [PATCH 2/3] coccinelle: double_lock: improve performance when no double lock exists Sang-Heon Jeon
2026-07-25 19:48 ` Julia Lawall
2026-07-26 10:28 ` Sang-Heon Jeon
2026-07-25 11:32 ` [PATCH 3/3] coccinelle: misc: minmax: improve performance when no candidate exists Sang-Heon Jeon
2026-07-26 16:11 ` Julia Lawall
2026-07-26 16:28 ` Sang-Heon Jeon
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=c5a73800-59cd-4870-ae57-11fe832054b9@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=ekffu200098@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
/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®