linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Leo Yan <leo.yan@linaro.org>, James Clark <james.clark@arm.com>
Subject: Re: [PATCH v4 0/3] perf tool: 'config3' attribute support
Date: Fri, 14 Oct 2022 12:25:37 -0300	[thread overview]
Message-ID: <Y0l/cc8MTNY8RQUl@kernel.org> (raw)
In-Reply-To: <20220914-arm-perf-tool-spe1-2-v2-v4-0-83c098e6212e@kernel.org>

Em Tue, Oct 04, 2022 at 02:12:34PM -0500, Rob Herring escreveu:
> This series is a fix to allow unknown 'configN' attrs and then extends 
> perf tool to support a new config3 attr.
> 
> The config3 support is RFC for context as the kernel side support[1] is 
> not yet accepted. Patch 1 is intended for 6.1.
> 
> [1] https://lore.kernel.org/all/20220825-arm-spe-v8-7-v1-0-c75b8d92e692@kernel.org/
> 
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Changes in v4:
> - Fix event parsing test segfault
> - Add 'config3' in event parsing tests
> - Link to v3: https://lore.kernel.org/r/20220914-arm-perf-tool-spe1-2-v2-v3-0-8189fc04dcc6@kernel.org

Thanks, applied.

- Arnaldo

 
> ---
> Rob Herring (3):
>       perf: Skip and warn on unknown format 'configN' attrs
>       perf tools: Sync perf_event_attr::config3 addition
>       perf: Add support for perf_event_attr::config3
> 
>  include/uapi/linux/perf_event.h       |  3 +++
>  tools/include/uapi/linux/perf_event.h |  3 +++
>  tools/perf/tests/parse-events.c       | 13 ++++++++++++-
>  tools/perf/util/parse-events.c        |  9 +++++++++
>  tools/perf/util/parse-events.h        |  1 +
>  tools/perf/util/parse-events.l        |  1 +
>  tools/perf/util/pmu.c                 | 20 ++++++++++++++++++++
>  tools/perf/util/pmu.h                 |  3 +++
>  tools/perf/util/pmu.l                 |  2 --
>  tools/perf/util/pmu.y                 | 15 ++++-----------
>  10 files changed, 56 insertions(+), 14 deletions(-)
> ---
> base-commit: 1c23f9e627a7b412978b4e852793c5e3c3efc555
> change-id: 20220914-arm-perf-tool-spe1-2-v2-cab789c5d598
> 
> Best regards,
> -- 
> Rob Herring <robh@kernel.org>

-- 

- Arnaldo

      parent reply	other threads:[~2022-10-14 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 19:12 [PATCH v4 0/3] perf tool: 'config3' attribute support Rob Herring
2022-10-04 19:12 ` [PATCH v4 1/3] perf: Skip and warn on unknown format 'configN' attrs Rob Herring
2022-10-04 19:12 ` [PATCH v4 2/3] perf tools: Sync perf_event_attr::config3 addition Rob Herring
2022-10-14 21:51   ` Arnaldo Carvalho de Melo
2022-10-14 22:05     ` Rob Herring
2022-10-04 19:12 ` [PATCH v4 3/3] perf: Add support for perf_event_attr::config3 Rob Herring
2022-10-14 15:25 ` Arnaldo Carvalho de Melo [this message]

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=Y0l/cc8MTNY8RQUl@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.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=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=robh@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).