DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, stephen@networkplumber.org
Subject: Re: [PATCH v2 3/3] bus/dpaa: enabling clang thread safety for locks
Date: Mon, 18 Nov 2024 19:06:52 +0100	[thread overview]
Message-ID: <6744132.4vTCxPXJkl@thomas> (raw)
In-Reply-To: <20241114074437.2943885-3-hemant.agrawal@nxp.com>

14/11/2024 08:44, Hemant Agrawal:
> To avoid regressions on this topic, could you look into enabling clang
> thread safety check?

This original question is replaced with a proper description of the change:

    bus/dpaa: enable clang thread safety check for FQ locks
    
    Enable "annotate_locks" for compile-time checks by clang.
    
    FQLOCK and FQUNLOCK need to be considered as lock functions
    that the clang analyzer can rely on.

> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Applied, thanks.



      reply	other threads:[~2024-11-18 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 16:14 [PATCH 1/2] bus/dpaa: fix lock condition during error handling Hemant Agrawal
2024-11-13 16:14 ` [PATCH 2/2] examples/l2fwd-event: fix spinlock handling Hemant Agrawal
2024-11-13 16:48 ` [PATCH 1/2] bus/dpaa: fix lock condition during error handling David Marchand
2024-11-14  7:45   ` Hemant Agrawal
2024-11-14  7:44 ` [PATCH v2 1/3] " Hemant Agrawal
2024-11-14  7:44   ` [PATCH v2 2/3] examples/l2fwd-event: fix spinlock handling Hemant Agrawal
2024-11-18  9:32     ` [EXTERNAL] " Jerin Jacob
2024-11-14  7:44   ` [PATCH v2 3/3] bus/dpaa: enabling clang thread safety for locks Hemant Agrawal
2024-11-18 18:06     ` Thomas Monjalon [this message]

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=6744132.4vTCxPXJkl@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=stephen@networkplumber.org \
    /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;
as well as URLs for NNTP newsgroup(s).