From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id BB704428CD; Tue, 4 Apr 2023 14:50:27 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B9D4441156; Tue, 4 Apr 2023 14:49:46 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 9BD3742D50 for ; Tue, 4 Apr 2023 14:49:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680612584; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ua9bxdTCIzphsmVe/7/8wVpV3aAfodxM+TLmq0GxFIQ=; b=XXWoJQFInroAKueLH6zKzgGPs2PsMyGZjWx0LUR3NuKuzoKtI4lz8ZR5e3zI9LlqwGCgmh jqjQNc91IApQ/gO20ejPqwXpLIT8CxYjltpSowcyfNOKwB+1/kDGwI8StNPv/PB4dROYak yxBTullrn2RbQfKtqnpH6K/FZbQAO3o= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-190-akPzZjAYP9yfrlN6jiCZ9w-1; Tue, 04 Apr 2023 08:49:38 -0400 X-MC-Unique: akPzZjAYP9yfrlN6jiCZ9w-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 736638030D0; Tue, 4 Apr 2023 12:49:38 +0000 (UTC) Received: from dmarchan.redhat.com (unknown [10.45.225.38]) by smtp.corp.redhat.com (Postfix) with ESMTP id 432EF492C13; Tue, 4 Apr 2023 12:49:37 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: thomas@monjalon.net, Dmitry Kozlyuk , Narcisa Ana Maria Vasile , Dmitry Malloy , Pallavi Kadam Subject: [PATCH v3 15/16] eal/windows: disable lock check on alarm code Date: Tue, 4 Apr 2023 14:48:39 +0200 Message-Id: <20230404124840.1898-16-david.marchand@redhat.com> In-Reply-To: <20230404124840.1898-1-david.marchand@redhat.com> References: <20230224081642.2566619-1-david.marchand@redhat.com> <20230404124840.1898-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org This code uses locks to implement synchronisation between two threads. There seems nothing wrong with it, just silence the clang lock check. Signed-off-by: David Marchand --- lib/eal/windows/eal_alarm.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/lib/eal/windows/eal_alarm.c b/lib/eal/windows/eal_alarm.c index 48203a2870..34b52380ce 100644 --- a/lib/eal/windows/eal_alarm.c +++ b/lib/eal/windows/eal_alarm.c @@ -224,6 +224,7 @@ struct intr_task { static void intr_thread_entry(void *arg) + __rte_no_thread_safety_analysis { struct intr_task *task = arg; task->func(task->arg); @@ -232,6 +233,7 @@ intr_thread_entry(void *arg) static int intr_thread_exec_sync(void (*func)(void *arg), void *arg) + __rte_no_thread_safety_analysis { struct intr_task task; int ret; -- 2.39.2