Message ID | 20231108215322.2845536-1-namhyung@kernel.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b129:0:b0:403:3b70:6f57 with SMTP id q9csp65060vqs; Wed, 8 Nov 2023 13:53:44 -0800 (PST) X-Google-Smtp-Source: AGHT+IE2n4X67Kt59UveIomhCLrmEb5u10V3bApadP3TVwqoHrwHPCFIcMqgWL9D5N/bJqtmmN8K X-Received: by 2002:a05:6a20:7fa5:b0:15d:8366:65be with SMTP id d37-20020a056a207fa500b0015d836665bemr5215746pzj.9.1699480424157; Wed, 08 Nov 2023 13:53:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1699480424; cv=none; d=google.com; s=arc-20160816; b=kFpPKK8FK0DfshC9rkQl/kUjE7Ogmq8whv4AwfS9sofMZMbUs1XUXT3NsfsxYL0zpX 5EddVWS5Oer/cIGSfaXtHtpJYUTBwg9bBIWcVSa6ZDbW2Iq+4g42ZFDm0oL9pIx/9Zxg pnpGCmT817JUnPhMuV1+/EaYukGnIt1kxWNHvRfHn9KAldDZiOBW/h5DSHF5l++ho91G s0uRmkgKTamaYgyh/XifCXar7GN9YtMDSoro7mAfSEOHJveoUpAoM56jmibvaXhMxQoj VgJrPha27aHBJo72/WkrvvHUIqj7YzlU3Sy4OKcTKEkmWuZIkKTHg84pscpRxe7cgO0C XRKA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:sender:dkim-signature; bh=8+1RUn6ye/V5oCXpT4AXN5Yt2m+B7UnFQxMDOfZORrg=; fh=pKNNmHIejYH3q6wrQJ9w9M1pkTrwzFNV0W34etTg3eY=; b=i1I7t5ll744Plhaj++4kuHI1NPadpJ8SDIlLn43SPWM7v7g3nhskqLZGDHSON1LiFe wyDmDSG5G3rh+k91nwdb9aRj0X4Cw5iPt3cKvpfPw04qiWXlJK2aoa+Fv3d/3wuqnvVQ D/VjL8YLy7capBmaR2VIC78eXcP8QEVlINcKOYgLCF6jSkhF/NWbt5okId7cQ+GxzK2M 6RAYCs05hRnHYGRMxb6PKsOYFeRgSxZtIUhk9dnlhqPlfYMmZXb9xIibEqlfT6ZJLsdv 6FaVRaydBYCvLQoX/MTgvE6LnIOIka1+eYRQKL1As3Jz/V7Tqs9Bg+UJy0unVcJvOvO2 wQiA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=XcVaQsRA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from fry.vger.email (fry.vger.email. [2620:137:e000::3:8]) by mx.google.com with ESMTPS id m19-20020aa78a13000000b006c34bf27348si12812598pfa.394.2023.11.08.13.53.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Nov 2023 13:53:44 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=XcVaQsRA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id B152D83B2E14; Wed, 8 Nov 2023 13:53:41 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229910AbjKHVx1 (ORCPT <rfc822;jaysivo@gmail.com> + 32 others); Wed, 8 Nov 2023 16:53:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32802 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229460AbjKHVx0 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 8 Nov 2023 16:53:26 -0500 Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 57B7B258A for <linux-kernel@vger.kernel.org>; Wed, 8 Nov 2023 13:53:24 -0800 (PST) Received: by mail-pg1-x529.google.com with SMTP id 41be03b00d2f7-5bd0631f630so160181a12.0 for <linux-kernel@vger.kernel.org>; Wed, 08 Nov 2023 13:53:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699480404; x=1700085204; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:sender:from:to:cc:subject:date:message-id:reply-to; bh=8+1RUn6ye/V5oCXpT4AXN5Yt2m+B7UnFQxMDOfZORrg=; b=XcVaQsRAQdI7aRmQVwJ0NyQGgdhNuLJ61Cgdkn9wCXn30j5CmhU+lIo5+X9g7tMnBi E8iemZZGHVFoKGwpXh+WWbY6FOOjKsvN9EI7EIz2LWehttpGZU8/LVH4ngT7AffDlKUS PdwI+Gokukiah6uC6L9PEb6IrPFcMsyzJzZArAd+BJcELZ8FIRO9F1LPU3x54CSPZJlp FhZuE2XwDoyVR56ihP5IoyzM7X+60UlxMYyTe8MqsULsZ9r9BIwkGUSSaIQbAQR7zCoc b9fzbQpZBV105EV4VzYQf9pJtHYIbB8RFxzws2wxvou3quqqlFtJqvaQSvuJwvvJY/bb UFCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699480404; x=1700085204; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:sender:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=8+1RUn6ye/V5oCXpT4AXN5Yt2m+B7UnFQxMDOfZORrg=; b=uq6TX8Qqq6qvRHJnP5HCOPcODvY8LNbM5iqmBW+/iGkVNgnuFspGXUfkUZ/LGpELt3 PJmqLfd4v3kF0VzB/Odj/+OrT6n9DWr8Z3kQNmdnUj32FFObHZfzONmHRNAg4hrQkHzw iY4DjMZZ/QTy3qeYL+qefl/a2g4XpBVA7nMkvMdsjgc+T3eAn3DThbGuHqLZMMi+5uo8 h1bHHfbLo40Fyluz8Q4g3rnVhnPU7q7+VosAlq2sLxN9LQH+6eO5IBK3IoRykOAZwgQn ybiyVOXF9oa32ovPgVhl7g2I/uLR1cZv+XZZOCVrnWYkyLOBmxLV++GxdAo8zxmX3s1A ek+Q== X-Gm-Message-State: AOJu0YxZ6EneREZY//FJ4m29UEHMmoBXymwXLeomcqW9FY5r4zWNsGqE 5Wih7gtlAGHlpoPL4XiWzcEsUuKIZ8E= X-Received: by 2002:a17:90a:d717:b0:280:2a3f:9938 with SMTP id y23-20020a17090ad71700b002802a3f9938mr10158599pju.12.1699480403564; Wed, 08 Nov 2023 13:53:23 -0800 (PST) Received: from bangji.corp.google.com ([2620:15c:2c0:5:555d:a196:40f8:b293]) by smtp.gmail.com with ESMTPSA id z23-20020a17090acb1700b00280cd18c161sm4469pjt.53.2023.11.08.13.53.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Nov 2023 13:53:23 -0800 (PST) Sender: Namhyung Kim <namhyung@gmail.com> From: Namhyung Kim <namhyung@kernel.org> To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@kernel.org>, Will Deacon <will@kernel.org> Cc: Waiman Long <longman@redhat.com>, Boqun Feng <boqun.feng@gmail.com>, LKML <linux-kernel@vger.kernel.org> Subject: [PATCH] locking/percpu-rwsem: Trigger contention tracepoints only if contended Date: Wed, 8 Nov 2023 13:53:22 -0800 Message-ID: <20231108215322.2845536-1-namhyung@kernel.org> X-Mailer: git-send-email 2.42.0.869.gea05f2083d-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Wed, 08 Nov 2023 13:53:41 -0800 (PST) X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on fry.vger.email X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1782034385460809058 X-GMAIL-MSGID: 1782034385460809058 |
Series |
locking/percpu-rwsem: Trigger contention tracepoints only if contended
|
|
Commit Message
Namhyung Kim
Nov. 8, 2023, 9:53 p.m. UTC
It mistakenly fires lock contention tracepoints always in the writer path.
It should be conditional on the try lock result.
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
kernel/locking/percpu-rwsem.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
Comments
Ping! On Wed, Nov 8, 2023 at 1:53 PM Namhyung Kim <namhyung@kernel.org> wrote: > > It mistakenly fires lock contention tracepoints always in the writer path. > It should be conditional on the try lock result. > > Signed-off-by: Namhyung Kim <namhyung@kernel.org> > --- > kernel/locking/percpu-rwsem.c | 11 ++++++++--- > 1 file changed, 8 insertions(+), 3 deletions(-) > > diff --git a/kernel/locking/percpu-rwsem.c b/kernel/locking/percpu-rwsem.c > index 185bd1c906b0..6083883c4fe0 100644 > --- a/kernel/locking/percpu-rwsem.c > +++ b/kernel/locking/percpu-rwsem.c > @@ -223,9 +223,10 @@ static bool readers_active_check(struct percpu_rw_semaphore *sem) > > void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > { > + bool contended = false; > + > might_sleep(); > rwsem_acquire(&sem->dep_map, 0, 0, _RET_IP_); > - trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); > > /* Notify readers to take the slow path. */ > rcu_sync_enter(&sem->rss); > @@ -234,8 +235,11 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > * Try set sem->block; this provides writer-writer exclusion. > * Having sem->block set makes new readers block. > */ > - if (!__percpu_down_write_trylock(sem)) > + if (!__percpu_down_write_trylock(sem)) { > + trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); > percpu_rwsem_wait(sem, /* .reader = */ false); > + contended = true; > + } > > /* smp_mb() implied by __percpu_down_write_trylock() on success -- D matches A */ > > @@ -247,7 +251,8 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > > /* Wait for all active readers to complete. */ > rcuwait_wait_event(&sem->writer, readers_active_check(sem), TASK_UNINTERRUPTIBLE); > - trace_contention_end(sem, 0); > + if (contended) > + trace_contention_end(sem, 0); > } > EXPORT_SYMBOL_GPL(percpu_down_write); > > -- > 2.42.0.869.gea05f2083d-goog >
Hello, On Mon, Nov 20, 2023 at 12:28 PM Namhyung Kim <namhyung@kernel.org> wrote: > > Ping! > > On Wed, Nov 8, 2023 at 1:53 PM Namhyung Kim <namhyung@kernel.org> wrote: > > > > It mistakenly fires lock contention tracepoints always in the writer path. > > It should be conditional on the try lock result. Can anybody take a look at this? This makes a large noise in the lock contention result. Thanks, Namhyung > > > > Signed-off-by: Namhyung Kim <namhyung@kernel.org> > > --- > > kernel/locking/percpu-rwsem.c | 11 ++++++++--- > > 1 file changed, 8 insertions(+), 3 deletions(-) > > > > diff --git a/kernel/locking/percpu-rwsem.c b/kernel/locking/percpu-rwsem.c > > index 185bd1c906b0..6083883c4fe0 100644 > > --- a/kernel/locking/percpu-rwsem.c > > +++ b/kernel/locking/percpu-rwsem.c > > @@ -223,9 +223,10 @@ static bool readers_active_check(struct percpu_rw_semaphore *sem) > > > > void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > > { > > + bool contended = false; > > + > > might_sleep(); > > rwsem_acquire(&sem->dep_map, 0, 0, _RET_IP_); > > - trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); > > > > /* Notify readers to take the slow path. */ > > rcu_sync_enter(&sem->rss); > > @@ -234,8 +235,11 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > > * Try set sem->block; this provides writer-writer exclusion. > > * Having sem->block set makes new readers block. > > */ > > - if (!__percpu_down_write_trylock(sem)) > > + if (!__percpu_down_write_trylock(sem)) { > > + trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); > > percpu_rwsem_wait(sem, /* .reader = */ false); > > + contended = true; > > + } > > > > /* smp_mb() implied by __percpu_down_write_trylock() on success -- D matches A */ > > > > @@ -247,7 +251,8 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > > > > /* Wait for all active readers to complete. */ > > rcuwait_wait_event(&sem->writer, readers_active_check(sem), TASK_UNINTERRUPTIBLE); > > - trace_contention_end(sem, 0); > > + if (contended) > > + trace_contention_end(sem, 0); > > } > > EXPORT_SYMBOL_GPL(percpu_down_write); > > > > -- > > 2.42.0.869.gea05f2083d-goog > >
On 2/27/24 18:02, Namhyung Kim wrote: > Hello, > > On Mon, Nov 20, 2023 at 12:28 PM Namhyung Kim <namhyung@kernel.org> wrote: >> Ping! >> >> On Wed, Nov 8, 2023 at 1:53 PM Namhyung Kim <namhyung@kernel.org> wrote: >>> It mistakenly fires lock contention tracepoints always in the writer path. >>> It should be conditional on the try lock result. > Can anybody take a look at this? This makes a large noise > in the lock contention result. > > Thanks, > Namhyung > >>> Signed-off-by: Namhyung Kim <namhyung@kernel.org> >>> --- >>> kernel/locking/percpu-rwsem.c | 11 ++++++++--- >>> 1 file changed, 8 insertions(+), 3 deletions(-) >>> >>> diff --git a/kernel/locking/percpu-rwsem.c b/kernel/locking/percpu-rwsem.c >>> index 185bd1c906b0..6083883c4fe0 100644 >>> --- a/kernel/locking/percpu-rwsem.c >>> +++ b/kernel/locking/percpu-rwsem.c >>> @@ -223,9 +223,10 @@ static bool readers_active_check(struct percpu_rw_semaphore *sem) >>> >>> void __sched percpu_down_write(struct percpu_rw_semaphore *sem) >>> { >>> + bool contended = false; >>> + >>> might_sleep(); >>> rwsem_acquire(&sem->dep_map, 0, 0, _RET_IP_); >>> - trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); >>> >>> /* Notify readers to take the slow path. */ >>> rcu_sync_enter(&sem->rss); >>> @@ -234,8 +235,11 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) >>> * Try set sem->block; this provides writer-writer exclusion. >>> * Having sem->block set makes new readers block. >>> */ >>> - if (!__percpu_down_write_trylock(sem)) >>> + if (!__percpu_down_write_trylock(sem)) { >>> + trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); >>> percpu_rwsem_wait(sem, /* .reader = */ false); >>> + contended = true; >>> + } >>> >>> /* smp_mb() implied by __percpu_down_write_trylock() on success -- D matches A */ >>> >>> @@ -247,7 +251,8 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) >>> >>> /* Wait for all active readers to complete. */ >>> rcuwait_wait_event(&sem->writer, readers_active_check(sem), TASK_UNINTERRUPTIBLE); >>> - trace_contention_end(sem, 0); >>> + if (contended) >>> + trace_contention_end(sem, 0); >>> } >>> EXPORT_SYMBOL_GPL(percpu_down_write); >>> >>> -- >>> 2.42.0.869.gea05f2083d-goog Yes, that makes sense. Sorry for missing this patch. Reviewed-by: Waiman Long <longman@redhat.com>
On Tue, Feb 27, 2024 at 4:19 PM Waiman Long <longman@redhat.com> wrote: > > > On 2/27/24 18:02, Namhyung Kim wrote: > > Hello, > > > > On Mon, Nov 20, 2023 at 12:28 PM Namhyung Kim <namhyung@kernel.org> wrote: > >> Ping! > >> > >> On Wed, Nov 8, 2023 at 1:53 PM Namhyung Kim <namhyung@kernel.org> wrote: > >>> It mistakenly fires lock contention tracepoints always in the writer path. > >>> It should be conditional on the try lock result. > > Can anybody take a look at this? This makes a large noise > > in the lock contention result. > > > > Thanks, > > Namhyung > > > >>> Signed-off-by: Namhyung Kim <namhyung@kernel.org> > >>> --- > >>> kernel/locking/percpu-rwsem.c | 11 ++++++++--- > >>> 1 file changed, 8 insertions(+), 3 deletions(-) > >>> > >>> diff --git a/kernel/locking/percpu-rwsem.c b/kernel/locking/percpu-rwsem.c > >>> index 185bd1c906b0..6083883c4fe0 100644 > >>> --- a/kernel/locking/percpu-rwsem.c > >>> +++ b/kernel/locking/percpu-rwsem.c > >>> @@ -223,9 +223,10 @@ static bool readers_active_check(struct percpu_rw_semaphore *sem) > >>> > >>> void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > >>> { > >>> + bool contended = false; > >>> + > >>> might_sleep(); > >>> rwsem_acquire(&sem->dep_map, 0, 0, _RET_IP_); > >>> - trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); > >>> > >>> /* Notify readers to take the slow path. */ > >>> rcu_sync_enter(&sem->rss); > >>> @@ -234,8 +235,11 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > >>> * Try set sem->block; this provides writer-writer exclusion. > >>> * Having sem->block set makes new readers block. > >>> */ > >>> - if (!__percpu_down_write_trylock(sem)) > >>> + if (!__percpu_down_write_trylock(sem)) { > >>> + trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); > >>> percpu_rwsem_wait(sem, /* .reader = */ false); > >>> + contended = true; > >>> + } > >>> > >>> /* smp_mb() implied by __percpu_down_write_trylock() on success -- D matches A */ > >>> > >>> @@ -247,7 +251,8 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > >>> > >>> /* Wait for all active readers to complete. */ > >>> rcuwait_wait_event(&sem->writer, readers_active_check(sem), TASK_UNINTERRUPTIBLE); > >>> - trace_contention_end(sem, 0); > >>> + if (contended) > >>> + trace_contention_end(sem, 0); > >>> } > >>> EXPORT_SYMBOL_GPL(percpu_down_write); > >>> > >>> -- > >>> 2.42.0.869.gea05f2083d-goog > > Yes, that makes sense. Sorry for missing this patch. > > Reviewed-by: Waiman Long <longman@redhat.com> Thanks for your review. Namhyung
* Waiman Long <longman@redhat.com> wrote: > > On 2/27/24 18:02, Namhyung Kim wrote: > > Hello, > > > > On Mon, Nov 20, 2023 at 12:28 PM Namhyung Kim <namhyung@kernel.org> wrote: > > > Ping! > > > > > > On Wed, Nov 8, 2023 at 1:53 PM Namhyung Kim <namhyung@kernel.org> wrote: > > > > It mistakenly fires lock contention tracepoints always in the writer path. > > > > It should be conditional on the try lock result. > > Can anybody take a look at this? This makes a large noise > > in the lock contention result. > > > > Thanks, > > Namhyung > > > > > > Signed-off-by: Namhyung Kim <namhyung@kernel.org> > > > > --- > > > > kernel/locking/percpu-rwsem.c | 11 ++++++++--- > > > > 1 file changed, 8 insertions(+), 3 deletions(-) > > > > > > > > diff --git a/kernel/locking/percpu-rwsem.c b/kernel/locking/percpu-rwsem.c > > > > index 185bd1c906b0..6083883c4fe0 100644 > > > > --- a/kernel/locking/percpu-rwsem.c > > > > +++ b/kernel/locking/percpu-rwsem.c > > > > @@ -223,9 +223,10 @@ static bool readers_active_check(struct percpu_rw_semaphore *sem) > > > > > > > > void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > > > > { > > > > + bool contended = false; > > > > + > > > > might_sleep(); > > > > rwsem_acquire(&sem->dep_map, 0, 0, _RET_IP_); > > > > - trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); > > > > > > > > /* Notify readers to take the slow path. */ > > > > rcu_sync_enter(&sem->rss); > > > > @@ -234,8 +235,11 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > > > > * Try set sem->block; this provides writer-writer exclusion. > > > > * Having sem->block set makes new readers block. > > > > */ > > > > - if (!__percpu_down_write_trylock(sem)) > > > > + if (!__percpu_down_write_trylock(sem)) { > > > > + trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); > > > > percpu_rwsem_wait(sem, /* .reader = */ false); > > > > + contended = true; > > > > + } > > > > > > > > /* smp_mb() implied by __percpu_down_write_trylock() on success -- D matches A */ > > > > > > > > @@ -247,7 +251,8 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) > > > > > > > > /* Wait for all active readers to complete. */ > > > > rcuwait_wait_event(&sem->writer, readers_active_check(sem), TASK_UNINTERRUPTIBLE); > > > > - trace_contention_end(sem, 0); > > > > + if (contended) > > > > + trace_contention_end(sem, 0); > > > > } > > > > EXPORT_SYMBOL_GPL(percpu_down_write); > > > > > > > > -- > > > > 2.42.0.869.gea05f2083d-goog > > Yes, that makes sense. Sorry for missing this patch. > > Reviewed-by: Waiman Long <longman@redhat.com> Applied to tip:locking/core, thanks guys! Ingo
diff --git a/kernel/locking/percpu-rwsem.c b/kernel/locking/percpu-rwsem.c index 185bd1c906b0..6083883c4fe0 100644 --- a/kernel/locking/percpu-rwsem.c +++ b/kernel/locking/percpu-rwsem.c @@ -223,9 +223,10 @@ static bool readers_active_check(struct percpu_rw_semaphore *sem) void __sched percpu_down_write(struct percpu_rw_semaphore *sem) { + bool contended = false; + might_sleep(); rwsem_acquire(&sem->dep_map, 0, 0, _RET_IP_); - trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); /* Notify readers to take the slow path. */ rcu_sync_enter(&sem->rss); @@ -234,8 +235,11 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) * Try set sem->block; this provides writer-writer exclusion. * Having sem->block set makes new readers block. */ - if (!__percpu_down_write_trylock(sem)) + if (!__percpu_down_write_trylock(sem)) { + trace_contention_begin(sem, LCB_F_PERCPU | LCB_F_WRITE); percpu_rwsem_wait(sem, /* .reader = */ false); + contended = true; + } /* smp_mb() implied by __percpu_down_write_trylock() on success -- D matches A */ @@ -247,7 +251,8 @@ void __sched percpu_down_write(struct percpu_rw_semaphore *sem) /* Wait for all active readers to complete. */ rcuwait_wait_event(&sem->writer, readers_active_check(sem), TASK_UNINTERRUPTIBLE); - trace_contention_end(sem, 0); + if (contended) + trace_contention_end(sem, 0); } EXPORT_SYMBOL_GPL(percpu_down_write);