From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, masahiroy@kernel.org,
leo.yan@linaro.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>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/1] perf tools: Add a place to put kernel config fragments for test runs
Date: Fri, 28 Jul 2023 10:29:20 -0300 [thread overview]
Message-ID: <ZMPCsEeO1Xad/pR6@kernel.org> (raw)
In-Reply-To: <85fad198-278a-aea2-3ada-f4f6a31f02ef@arm.com>
Em Fri, Jul 28, 2023 at 11:48:34AM +0100, James Clark escreveu:
>
>
> On 30/06/2023 09:04, James Clark wrote:
> >
> >
> > On 29/06/2023 23:03, Namhyung Kim wrote:
> >> Hi James,
> >>
> >> On Wed, Jun 28, 2023 at 3:53 AM James Clark <james.clark@arm.com> wrote:
> >>>
> >>> 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.
> >>
> >> I missed the RFC, sorry. Could you please add a link for that?
> >>
> >> Thanks,
> >> Namhyung
> >
> > Yep, it's here:
> > https://lore.kernel.org/lkml/d02cce4a-47b1-a776-0d3a-a6a7c9a4d8fd@arm.com/T/
> >
>
> Hi Arnaldo,
>
> Any interest in taking this one?
Yeah, looks useful, we can go on from this starting point and improve
it.
I merged it into perf-tools-next.
Thanks,
- Arnaldo
> Thanks
> James
>
> >>
> >>
> >>>
> >>> 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
> >>>
--
- Arnaldo
next prev parent reply other threads:[~2023-07-28 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 10:53 [PATCH v1 0/1] perf tools: Add a place to put kernel config fragments for test runs James Clark
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 [this message]
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=ZMPCsEeO1Xad/pR6@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=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;
as well as URLs for NNTP newsgroup(s).