From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: [PATCH 0/4] perf tools: Remove needless affinity setup/cleanup for pid targets
Date: Mon, 17 Jan 2022 13:09:27 -0300 [thread overview]
Message-ID: <20220117160931.1191712-1-acme@kernel.org> (raw)
From: Arnaldo Carvalho de Melo <acme@redhat.com>
Hi,
Continuing with the removal of needless affinity setup/cleanup
for pid targets, please ack.
- Arnaldo
Arnaldo Carvalho de Melo (4):
perf affinity: Allow passing a NULL arg to affinity__cleanup()
perf stat: No need to setup affinities when starting a workload
perf evlist: No need to setup affinities when enabling events for pid
targets
perf evlist: No need to setup affinities when disabling events for pid
targets
tools/perf/builtin-stat.c | 17 ++++++++++-------
tools/perf/util/affinity.c | 8 +++++++-
tools/perf/util/evlist.c | 28 ++++++++++++++++++----------
3 files changed, 35 insertions(+), 18 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-17 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 16:09 Arnaldo Carvalho de Melo [this message]
2022-01-17 16:09 ` [PATCH 1/4] perf affinity: Allow passing a NULL arg to affinity__cleanup() Arnaldo Carvalho de Melo
2022-01-17 16:09 ` [PATCH 2/4] perf stat: No need to setup affinities when starting a workload Arnaldo Carvalho de Melo
2022-01-17 16:09 ` [PATCH 3/4] perf evlist: No need to setup affinities when enabling events for pid targets Arnaldo Carvalho de Melo
2022-01-17 16:09 ` [PATCH 4/4] perf evlist: No need to setup affinities when disabling " Arnaldo Carvalho de Melo
2022-01-17 16:15 ` [PATCH 0/4] perf tools: Remove needless affinity setup/cleanup " Ian Rogers
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=20220117160931.1191712-1-acme@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=andi@firstfloor.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.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.