From: Leon Romanovsky <leon@kernel.org>
To: Timothy Day <timday@thelustrecollective.com>
Cc: Michael Margolin <mrgolin@amazon.com>,
Jason Gunthorpe <jgg@nvidia.com>,
linux-rdma@vger.kernel.org, Gal Pressman <gal.pressman@linux.dev>,
Yossi Leybovich <sleybo@amazon.com>,
Marco Elver <elver@google.com>
Subject: Re: [PATCH v1 0/5] Support Clang context analysis for RDMA/efa
Date: Tue, 21 Jul 2026 14:10:30 +0300 [thread overview]
Message-ID: <20260721111030.GH110966@unreal> (raw)
In-Reply-To: <20260717031658.477397-1-timday@thelustrecollective.com>
On Thu, Jul 16, 2026 at 11:16:53PM -0400, Timothy Day wrote:
> Hi,
>
> This series adds annotations for Clang's context analysis to the
> RDMA/efa driver.
>
> Clang context analysis was recently added in a series by Marco
> Elver [1]. This allows the compiler to validate different
> locking patterns at compile time. This series enables context
> analysis and adds new annotations.
>
> The series was built with Clang 23 (since the minimum Clang
> version for this feature was recently bumped to 23 in 7.2+ [2])
> with CONFIG_WARN_CONTEXT_ANALYSIS enabled. I based this series
> on rdma/for-next.
>
> I'd appreciate reviews and suggestions. I'm especially interested
> in suggestions on how we can make this easier to enable in other
> parts of the rdma subsystem.
Yes, this is precisely why I'm not rushing to apply it. It would
be far more compelling to first apply this context analysis to
drivers/infiniband/core, so we can evaluate both its benefits and
drawbacks.
On the other hand, converting drivers incrementally is the safer
approach.
Thanks
>
> Thanks!
>
> [1] https://lore.kernel.org/lkml/20251219154418.3592607-1-elver@google.com/
> [2] https://lore.kernel.org/all/20260515124426.2227783-1-elver@google.com/
>
> Timothy Day (5):
> RDMA/efa: mark mmio_read seq_num as guarded by mmio_read lock
> RDMA/efa: mark comp_ctx_pool* as guarded by comp_ctx_lock
> RDMA/efa: mark admin CQ consumer state as guarded by the ACQ lock
> RDMA/efa: mark admin SQ producer state as guarded by the ASQ lock
> RDMA/efa: enable context analysis support for efa driver
>
> drivers/infiniband/hw/efa/Makefile | 2 ++
> drivers/infiniband/hw/efa/efa_com.c | 33 +++++++++++++++++------------
> drivers/infiniband/hw/efa/efa_com.h | 14 ++++++------
> 3 files changed, 29 insertions(+), 20 deletions(-)
>
> --
> 2.39.5
>
next prev parent reply other threads:[~2026-07-21 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 3:16 [PATCH v1 0/5] Support Clang context analysis for RDMA/efa Timothy Day
2026-07-17 3:16 ` [PATCH v1 1/5] RDMA/efa: mark mmio_read seq_num as guarded by mmio_read lock Timothy Day
2026-07-17 3:16 ` [PATCH v1 2/5] RDMA/efa: mark comp_ctx_pool* as guarded by comp_ctx_lock Timothy Day
2026-07-17 3:16 ` [PATCH v1 3/5] RDMA/efa: mark admin CQ consumer state as guarded by the ACQ lock Timothy Day
2026-07-17 3:16 ` [PATCH v1 4/5] RDMA/efa: mark admin SQ producer state as guarded by the ASQ lock Timothy Day
2026-07-17 3:16 ` [PATCH v1 5/5] RDMA/efa: enable context analysis support for efa driver Timothy Day
2026-07-21 11:10 ` Leon Romanovsky [this message]
2026-07-21 20:27 ` [PATCH v1 0/5] Support Clang context analysis for RDMA/efa Timothy Day
2026-07-22 7:21 ` Leon Romanovsky
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=20260721111030.GH110966@unreal \
--to=leon@kernel.org \
--cc=elver@google.com \
--cc=gal.pressman@linux.dev \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mrgolin@amazon.com \
--cc=sleybo@amazon.com \
--cc=timday@thelustrecollective.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