Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4378638imw; Tue, 12 Jul 2022 07:02:53 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vTpfJQru2t2jghhPyx48g3CAgFCMJhDKLxJnmq3nKqtFBxjgzP1SxLjvK3igZQPcBm5r1I X-Received: by 2002:a17:906:cc46:b0:72b:83d4:de11 with SMTP id mm6-20020a170906cc4600b0072b83d4de11mr2451373ejb.428.1657634572964; Tue, 12 Jul 2022 07:02:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1657634572; cv=none; d=google.com; s=arc-20160816; b=PVTenii0Tbb4aoywLE5/pnjMVThpJl1eFTpbg3uLDg4jZUTZUh6m04Xp9HgfKMqBKL rrfGVZMylD5FWd7++dyNOuUG5g7YECfNwuGx66XCDX8tQSfnyG28XcFXpbMf5NU+74U2 bTvHZX9i1WqsACHgWgmB74iYIg3o6CEIXwaWrZNQjlSg3mp8IW8va+kIO9TguluLjrX3 F1feGUcnITZF0qNDat6Ka7cd8R7eaW2qyYB+wpZgYHd4qwz9umXP35XumPfIAQqSRfF0 NmK/CvSpo8DnLL3j59SdvUXFx9nw556vDTNXZSMiYff35EbmCIzefmd09qS3fF0PsTg4 Sn8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=ALyPmALyKUZN850RRfbsMebRjTXHId7O0aEtI7++nZc=; b=lB+K09e/EQh1+uXzduny0yCVHivIAY7Z6WPr34DfpGVmQvyHphHETAqB8j/8aV3aj2 0oxkx3Wx1fnqsHWEMqLg2sBUxFC0BJmY+dezkcKk332f1PWZFU3N/Br4hKCdaq69qcLM i6sAf/aYaUT4YnMC+aj3jWjafQQ1WR2+YsK4TlugWyeMAJoFO1LtzhtFuZKYZWR1rPFm PiZFXZgR9vDBw1445Ph4uf/MjXTMILZ5qKY37oBOphpaQEaCdXe0pgYk/mScHdNxKxXf egAYC2i5qnbxD6EjLgFNmWpyREsu2uTrY32nA5+lutmOPx02TPLrWIGAxWGKSjzJjUUI 4tmQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=LSt+DLU3; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a19-20020a170906671300b0072b10e05120si2700695ejp.297.2022.07.12.07.02.21; Tue, 12 Jul 2022 07:02:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=LSt+DLU3; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233382AbiGLNlf (ORCPT + 99 others); Tue, 12 Jul 2022 09:41:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55302 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233349AbiGLNk4 (ORCPT ); Tue, 12 Jul 2022 09:40:56 -0400 Received: from mail-yw1-x112b.google.com (mail-yw1-x112b.google.com [IPv6:2607:f8b0:4864:20::112b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8BC73B8530 for ; Tue, 12 Jul 2022 06:40:34 -0700 (PDT) Received: by mail-yw1-x112b.google.com with SMTP id 00721157ae682-31c86fe1dddso81423847b3.1 for ; Tue, 12 Jul 2022 06:40:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ALyPmALyKUZN850RRfbsMebRjTXHId7O0aEtI7++nZc=; b=LSt+DLU33Q6liALS8BuSSMkfOKSlRWDFuTo7po1O26Fv7bk7ore1ydtL7Hkh54hx5B 9uSRjCaDwCvwdfWSzS7lnufwTmWr2b2BeYWR5YFP9ZU8F9VUUXmk6Zu5giNcEj2YbgpC uI4p1/JHiKYlEhx0fK1shW+TiQcG27FxZBVsXr+bZEYrVso0bpBwSBWJ2SnXgjmK3o2a TljCQ3HgMAtH+5k9+nmdR7HTEIpmR3g8H3YU3v/0m4e+3pVXNggO7+TOdghExzxY46ET DIp6u0LHdi2CFsZzjm9ZOB6D+HRRffEUqutrzlU2tzRGZr0L4jryw4F7HNyo/VTj61UD CAVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ALyPmALyKUZN850RRfbsMebRjTXHId7O0aEtI7++nZc=; b=ad/s7U1yE3IjasSEsjIVEqwEFNmwRv86FPk7xCxMogqdUI9RQ3JPy4xHc9eqiRn8Cm TELMT+ZuXI/sLDvx0x2Jte509GGZ0mhQ3y7iCp65+hQUMpxnhHQdBtanKqvhdhsk9ae8 y8HNjpLQOyhfaCzt3VKE6kbVA5mc/KqLjjPqA7wf8m4vlqdmT8z6ofrTU9GlzTpKEgvl QSvTrqrWo8CxpnMrCXDhuwIR2InH/N5fIKJYzcuQSehqO57GF4dE5e37USjlwh7IOLCd 4e6gWkw+rAOD5oggVCwbaHDzK5ieLFcJS1PLaBEHCM97HDLfLBahF11kSpfZRVib9Zik xmHQ== X-Gm-Message-State: AJIora8M6iMLLhcJ/uFL4KLiAx+e5XRRrSNHlMMvco01jt1uL+shFMlS 4egSL3i+lhlTPnMpgHVETK4l609Kvsu3822khHJAEQ== X-Received: by 2002:a81:98d:0:b0:31c:921c:9783 with SMTP id 135-20020a81098d000000b0031c921c9783mr25237173ywj.316.1657633233606; Tue, 12 Jul 2022 06:40:33 -0700 (PDT) MIME-Version: 1.0 References: <20220704150514.48816-1-elver@google.com> In-Reply-To: <20220704150514.48816-1-elver@google.com> From: Marco Elver Date: Tue, 12 Jul 2022 15:39:57 +0200 Message-ID: Subject: Re: [PATCH v3 00/14] perf/hw_breakpoint: Optimize for thousands of tasks To: elver@google.com, Peter Zijlstra , Frederic Weisbecker , Ingo Molnar Cc: Thomas Gleixner , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Dmitry Vyukov , Michael Ellerman , linuxppc-dev@lists.ozlabs.org, linux-perf-users@vger.kernel.org, x86@kernel.org, linux-sh@vger.kernel.org, kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 4 Jul 2022 at 17:05, Marco Elver wrote: > > The hw_breakpoint subsystem's code has seen little change in over 10 > years. In that time, systems with >100s of CPUs have become common, > along with improvements to the perf subsystem: using breakpoints on > thousands of concurrent tasks should be a supported usecase. [...] > Marco Elver (14): > perf/hw_breakpoint: Add KUnit test for constraints accounting > perf/hw_breakpoint: Provide hw_breakpoint_is_used() and use in test > perf/hw_breakpoint: Clean up headers > perf/hw_breakpoint: Optimize list of per-task breakpoints > perf/hw_breakpoint: Mark data __ro_after_init > perf/hw_breakpoint: Optimize constant number of breakpoint slots > perf/hw_breakpoint: Make hw_breakpoint_weight() inlinable > perf/hw_breakpoint: Remove useless code related to flexible > breakpoints > powerpc/hw_breakpoint: Avoid relying on caller synchronization > locking/percpu-rwsem: Add percpu_is_write_locked() and > percpu_is_read_locked() > perf/hw_breakpoint: Reduce contention with large number of tasks > perf/hw_breakpoint: Introduce bp_slots_histogram > perf/hw_breakpoint: Optimize max_bp_pinned_slots() for CPU-independent > task targets > perf/hw_breakpoint: Optimize toggle_bp_slot() for CPU-independent task > targets [...] This is ready from our side, and given the silence, assume it's ready to pick up and/or have a maintainer take a look. Since this is mostly kernel/events, would -tip/perf/core be appropriate? Thanks, -- Marco