From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH RFC v1 2/3] perf: Add perf_event_attr::config3
Date: Thu, 25 Aug 2022 16:53:11 -0300 [thread overview]
Message-ID: <YwfTJ3k1zgTcejEn@kernel.org> (raw)
In-Reply-To: <CAL_JsqKdEkA+SGRd+P=WJnZE1YUuMjyPz5JwKz6cttuJ5hA_SQ@mail.gmail.com>
Em Thu, Aug 25, 2022 at 02:43:42PM -0500, Rob Herring escreveu:
> On Thu, Aug 25, 2022 at 2:31 PM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > Em Thu, Aug 25, 2022 at 01:08:01PM -0500, Rob Herring escreveu:
> > > Arm SPEv1.2 adds another 64-bits of event filtering control. As the
> > > existing perf_event_attr::configN fields are all used up for SPE PMU, an
> > > additional field is needed. Add a new 'config3' field.
> > Try not to have tools/ and kernel code in the same patch, else you'll
> > burden kernel developers into testing tools/, which so far has been
> > refrained.
> I knew that, but assumed the header was special...
So, we have tools/perf/check-headers.sh for that purpose, so that tools
developers can have the opportunity to see that the kernel ABI changed,
think about it, check what is needed to best support the new kernel ABI,
etc.
I really love when kernel developers take the time and help with
supporting new features by working on the tools/ bits, that would be
perfect!
But, as we saw just a few days ago, when changes were made in the kernel
and in tools/ in tandem, tools/ got broken just before -rc2:
"perf tools: Fix compile error for x86"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cfd2b5c1106fa20254d9f24970232cdf24860005>
So it seems better to first do the kernel work, then do the user part,
to avoid burdening kernel developers with tools/ work.
- Arnaldo
next prev parent reply other threads:[~2022-08-25 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 18:07 [PATCH RFC v1 0/3] perf: Arm SPEv1.2 support Rob Herring
2022-08-25 18:08 ` [PATCH RFC v1 1/3] perf: arm_spe: Support new SPEv1.2/v8.7 'not taken' event Rob Herring
2022-08-25 18:08 ` [PATCH RFC v1 2/3] perf: Add perf_event_attr::config3 Rob Herring
2022-08-25 19:31 ` Arnaldo Carvalho de Melo
2022-08-25 19:43 ` Rob Herring
2022-08-25 19:53 ` Arnaldo Carvalho de Melo [this message]
2022-08-31 19:06 ` Rob Herring
2022-08-31 20:07 ` Arnaldo Carvalho de Melo
2022-08-25 18:08 ` [PATCH RFC v1 3/3] perf: arm_spe: Add support for SPEv1.2 inverted event filtering Rob Herring
2022-09-05 14:55 ` James Clark
2022-09-06 13:48 ` Rob Herring
2022-09-12 8:53 ` Leo Yan
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=YwfTJ3k1zgTcejEn@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=will@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 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).