From: James Clark <james.clark@arm.com>
To: linux-perf-users@vger.kernel.org, acme@kernel.org,
masahiroy@kernel.org, leo.yan@linaro.org, broonie@kernel.org,
Aishwarya.TCV@arm.com
Cc: James Clark <james.clark@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/1] perf tools: Add a place to put kernel config fragments for test runs
Date: Wed, 28 Jun 2023 11:53:01 +0100 [thread overview]
Message-ID: <20230628105303.4053478-1-james.clark@arm.com> (raw)
Changes since RFC:
* Changed arch filename convention to use the ARCH= build time values
instead of uname
It seems like there were no objections on the RFC, apart from maybe
changing the perf tests to run as a kself test. But that's probably not
going to happen for a while, if ever, and these fragments can always
be moved in that case.
James Clark (1):
perf tools: Add a place to put kernel config fragments for test runs
tools/perf/tests/config-fragments/README | 7 +++++++
tools/perf/tests/config-fragments/arm64 | 1 +
tools/perf/tests/config-fragments/config | 11 +++++++++++
3 files changed, 19 insertions(+)
create mode 100644 tools/perf/tests/config-fragments/README
create mode 100644 tools/perf/tests/config-fragments/arm64
create mode 100644 tools/perf/tests/config-fragments/config
base-commit: ad5f604e186ac08d12c401e34ea96c09c38ddbc5
--
2.34.1
next reply other threads:[~2023-06-28 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 10:53 James Clark [this message]
2023-06-28 10:53 ` [PATCH v1 1/1] " James Clark
2023-06-29 22:03 ` [PATCH v1 0/1] " Namhyung Kim
2023-06-30 8:04 ` James Clark
2023-07-28 10:48 ` James Clark
2023-07-28 13:29 ` Arnaldo Carvalho de Melo
2023-07-28 13:59 ` James Clark
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=20230628105303.4053478-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=Aishwarya.TCV@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=broonie@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®