public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Clark Williams <williams@redhat.com>,
	Kate Carcia <kcarcia@redhat.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Athira Jajeev <atrajeev@linux.vnet.ibm.com>,
	Disha Goel <disgoel@linux.vnet.ibm.com>,
	Donglin Peng <dolinux.peng@gmail.com>,
	James Clark <james.clark@arm.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL] perf tools fixes for v6.1: 2nd batch
Date: Thu, 10 Nov 2022 14:28:31 -0300	[thread overview]
Message-ID: <20221110172831.369713-1-acme@kernel.org> (raw)

Hi Linus,

	Please consider pulling,

Best regards,

- Arnaldo

The following changes since commit 59f2f4b8a757412fce372f6d0767bdb55da127a8:

  fs/userfaultfd: Fix maple tree iterator in userfaultfd_unregister() (2022-11-07 12:58:26 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-tools-fixes-for-v6.1-2-2022-11-10

for you to fetch changes up to 94d957ae513fc420d0a5a9bac815eb49ffebb56f:

  perf tools: Add the include/perf/ directory to .gitignore (2022-11-08 18:54:41 -0300)

----------------------------------------------------------------
perf tools fixes for v6.1: 2nd batch

- Fix 'perf stat' crash with --per-node --metric-only in CSV mode, due
  to the AGGR_NODE slot in the 'aggr_header_csv' array not being set.

- Fix printing prefix in CSV output of 'perf stat' metrics in interval
  mode (-I), where an extra separator was being added to the start of
  some lines.

- Fix skipping branch stack sampling 'perf test' entry, that was using
  both --branch-any and --branch-filter, which can't be used together.

Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

----------------------------------------------------------------
Athira Rajeev (1):
      perf stat: Fix printing os->prefix in CSV metrics output

Donglin Peng (1):
      perf tools: Add the include/perf/ directory to .gitignore

James Clark (1):
      perf test: Fix skipping branch stack sampling test

Namhyung Kim (1):
      perf stat: Fix crash with --per-node --metric-only in CSV mode

 tools/perf/.gitignore                  | 1 +
 tools/perf/tests/shell/test_brstack.sh | 5 ++++-
 tools/perf/util/parse-branch-options.c | 4 +++-
 tools/perf/util/stat-display.c         | 6 ++++--
 4 files changed, 12 insertions(+), 4 deletions(-)

             reply	other threads:[~2022-11-10 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 17:28 Arnaldo Carvalho de Melo [this message]
2022-11-11 18:03 ` [GIT PULL] perf tools fixes for v6.1: 2nd batch pr-tracker-bot

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=20221110172831.369713-1-acme@kernel.org \
    --to=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=disgoel@linux.vnet.ibm.com \
    --cc=dolinux.peng@gmail.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@kernel.org \
    --cc=kcarcia@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=williams@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox