From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B340BC38A02 for ; Fri, 28 Oct 2022 19:49:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229974AbiJ1TtT (ORCPT ); Fri, 28 Oct 2022 15:49:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43706 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230041AbiJ1TtD (ORCPT ); Fri, 28 Oct 2022 15:49:03 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E0C83244C4E; Fri, 28 Oct 2022 12:48:55 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 744CFB82C99; Fri, 28 Oct 2022 19:48:54 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EAA46C433D6; Fri, 28 Oct 2022 19:48:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1666986533; bh=+tk8StPWL2eTUFNnVPmwC3O8GjHR+1aKv511/lqFp/s=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ETDNT6RvUhpwoIHjfUZ4ad34i2klkvjG7jEyF6CsiJRGFFcUoyfI76dwY2bBHTbfE X88UjVYP3bdNRZGXEYuaCZ04r5pkVj0P+ZBT8XAlp2MHwt96tPBc8o+3gr2ZZ4hAtH 5VLOAVO66VpkhI7YE7C28MIdFEmlrOhXhkFbh4/qLqpBJxhid90CvE31OWpF8JOWV5 TNLEKJSix3fHOqPoL4MIhgEs+x33qzciIwBWZ/gTe4NVmd4OZM8Z0P9IAeScQ2zjcP 8HLk2aUusCPR2Ybc9XmuC18NqEho+1NuFw3mBhweZyh1kCQ8nLv7bINlfqpdyREri5 Bwebv0GQccX8w== Received: by quaco.ghostprotocols.net (Postfix, from userid 1000) id 75DF74034E; Fri, 28 Oct 2022 16:48:50 -0300 (-03) Date: Fri, 28 Oct 2022 16:48:50 -0300 From: Arnaldo Carvalho de Melo To: Namhyung Kim Cc: Jiri Olsa , Ingo Molnar , Peter Zijlstra , LKML , Ian Rogers , Adrian Hunter , linux-perf-users@vger.kernel.org Subject: Re: [PATCH 0/4] perf lock contention: Small random fixes Message-ID: References: <20221028180128.3311491-1-namhyung@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221028180128.3311491-1-namhyung@kernel.org> X-Url: http://acmel.wordpress.com Precedence: bulk List-ID: X-Mailing-List: linux-perf-users@vger.kernel.org Em Fri, Oct 28, 2022 at 11:01:24AM -0700, Namhyung Kim escreveu: > Hello, > > This is a small update for the perf lock contention command. > > The first issue is from msan (memory sanitizer) related to uninitialized > memory access and use of variable length array. > > The other is to increase the default stack skip count to find appropriate > callers in most cases. > > You can get it from 'perf/lock-con-fix-v1' branch in > > git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git Thanks, applied. - Arnaldo > Thanks, > Namhyung > > > Namhyung Kim (4): > perf lock contention: Fix memory sanitizer issue > perf lock contention: Check --max-stack option > perf lock contention: Avoid variable length arrays > perf lock contention: Increase default stack skip to 4 > > tools/perf/builtin-lock.c | 30 +++++++++++++++++-- > tools/perf/util/bpf_lock_contention.c | 43 ++++++++++++++++++--------- > tools/perf/util/lock-contention.h | 2 +- > 3 files changed, 57 insertions(+), 18 deletions(-) > > > base-commit: a3a365655a28f12f07eddf4f3fd596987b175e1d > -- > 2.38.1.273.g43a17bfeac-goog -- - Arnaldo