From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-perf-users@vger.kernel.org, broonie@kernel.org,
Aishwarya.TCV@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: Re: [RFC PATCH] perf tools: Add a place to put kernel config fragments for test runs
Date: Wed, 14 Jun 2023 11:13:26 -0300 [thread overview]
Message-ID: <ZInLBt9q2F99gTg8@kernel.org> (raw)
In-Reply-To: <20230614140219.2335639-1-james.clark@arm.com>
Em Wed, Jun 14, 2023 at 03:02:19PM +0100, James Clark escreveu:
> We are currently keeping something like this in our CI because defconfig
> doesn't give full coverage. It's not complete yet, but is a starting
> point as a place to add to when a specific test needs something extra to
> run.
>
> The RFC is for discussion on folder placement and file naming etc.
Would be interesting to add the Kconfig maintainer to see if they have
an opinion, Masahiro?
- Arnaldo
> Signed-off-by: James Clark <james.clark@arm.com>
> ---
> tools/perf/tests/config-fragments/README | 7 +++++++
> tools/perf/tests/config-fragments/aarch64 | 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/aarch64
> create mode 100644 tools/perf/tests/config-fragments/config
>
> diff --git a/tools/perf/tests/config-fragments/README b/tools/perf/tests/config-fragments/README
> new file mode 100644
> index 000000000000..e816cfb1b96d
> --- /dev/null
> +++ b/tools/perf/tests/config-fragments/README
> @@ -0,0 +1,7 @@
> +This folder is for kernel config fragments that can be merged with
> +defconfig to give full test coverage of a perf test run. This is only
> +an optimistic set as some features require hardware support in order to
> +pass and not skip.
> +
> +'config' is shared across all platforms, and for arch specific files,
> +the file name should match that returned by 'uname -m'.
> diff --git a/tools/perf/tests/config-fragments/aarch64 b/tools/perf/tests/config-fragments/aarch64
> new file mode 100644
> index 000000000000..64c4ab17cd58
> --- /dev/null
> +++ b/tools/perf/tests/config-fragments/aarch64
> @@ -0,0 +1 @@
> +CONFIG_CORESIGHT_SOURCE_ETM4X=y
> diff --git a/tools/perf/tests/config-fragments/config b/tools/perf/tests/config-fragments/config
> new file mode 100644
> index 000000000000..c340b3195fca
> --- /dev/null
> +++ b/tools/perf/tests/config-fragments/config
> @@ -0,0 +1,11 @@
> +CONFIG_TRACEPOINTS=y
> +CONFIG_STACKTRACE=y
> +CONFIG_NOP_TRACER=y
> +CONFIG_RING_BUFFER=y
> +CONFIG_EVENT_TRACING=y
> +CONFIG_CONTEXT_SWITCH_TRACER=y
> +CONFIG_TRACING=y
> +CONFIG_GENERIC_TRACER=y
> +CONFIG_FTRACE=y
> +CONFIG_FTRACE_SYSCALLS=y
> +CONFIG_BRANCH_PROFILE_NONE=y
> --
> 2.34.1
>
--
- Arnaldo
next prev parent reply other threads:[~2023-06-14 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 14:02 [RFC PATCH] perf tools: Add a place to put kernel config fragments for test runs James Clark
2023-06-14 14:13 ` Arnaldo Carvalho de Melo [this message]
2023-06-14 14:19 ` James Clark
2023-06-15 1:26 ` Leo Yan
2023-06-15 11:19 ` Mark Brown
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=ZInLBt9q2F99gTg8@kernel.org \
--to=acme@kernel.org \
--cc=Aishwarya.TCV@arm.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=broonie@kernel.org \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.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;
as well as URLs for NNTP newsgroup(s).