All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 0/4] perf lock contention: Small random fixes
Date: Fri, 28 Oct 2022 16:48:50 -0300	[thread overview]
Message-ID: <Y1wyIsOqDt4iU134@kernel.org> (raw)
In-Reply-To: <20221028180128.3311491-1-namhyung@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

      parent reply	other threads:[~2022-10-28 19:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 18:01 [PATCH 0/4] perf lock contention: Small random fixes Namhyung Kim
2022-10-28 18:01 ` [PATCH 1/4] perf lock contention: Fix memory sanitizer issue Namhyung Kim
2022-10-28 18:01 ` [PATCH 2/4] perf lock contention: Check --max-stack option Namhyung Kim
2022-10-28 18:01 ` [PATCH 3/4] perf lock contention: Avoid variable length arrays Namhyung Kim
2022-10-28 18:01 ` [PATCH 4/4] perf lock contention: Increase default stack skip to 4 Namhyung Kim
2022-10-28 19:48 ` Arnaldo Carvalho de Melo [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=Y1wyIsOqDt4iU134@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.