linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Jing Zhang <renyu.zj@linux.alibaba.com>
Cc: Ian Rogers <irogers@google.com>,
	John Garry <john.g.garry@oracle.com>,
	 Will Deacon <will@kernel.org>, James Clark <james.clark@arm.com>,
	 Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	 Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
	 Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	 Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	 Adrian Hunter <adrian.hunter@intel.com>,
	linux-kernel@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org,  linux-doc@vger.kernel.org,
	Zhuo Song <zhuo.song@linux.alibaba.com>,
	 Shuai Xue <xueshuai@linux.alibaba.com>
Subject: Re: [PATCH v10 0/7] Add metrics for Arm CMN
Date: Tue, 26 Sep 2023 18:00:46 -0700	[thread overview]
Message-ID: <CAM9d7cjjSJybJEbSdBkVH3qx7RDqriv4tqBCNw1Yi9bAeUf3Yw@mail.gmail.com> (raw)
In-Reply-To: <f4812cce-14d2-9771-233f-b0db5af449be@linux.alibaba.com>

Hello,

On Mon, Sep 25, 2023 at 8:15 PM Jing Zhang <renyu.zj@linux.alibaba.com> wrote:
>
>
>
> 在 2023/9/26 上午12:37, Ian Rogers 写道:
> > On Sun, Sep 24, 2023 at 10:58 PM Jing Zhang <renyu.zj@linux.alibaba.com> wrote:
> >>
> >> Changes since v8:
> >> - Add fully match identifier check as suggested by Ian.
> >> - Link: https://lore.kernel.org/lkml/1695037955-107983-1-git-send-email-renyu.zj@linux.alibaba.com/
> >>
> >> Jing Zhang (7):
> >>   perf pmu: "Compat" supports regular expression matching identifiers
> >>   perf metric: "Compat" supports regular expression matching identifiers
> >>   perf jevents: Support EventidCode and NodeType
> >>   perf test: Make matching_pmu effective
> >>   perf test: Add pmu-event test for "Compat" and new event_field.
> >>   perf jevents: Add support for Arm CMN PMU aliasing
> >>   perf vendor events: Add JSON metrics for Arm CMN
> >
> > Thanks for the patience with all the to and fro. I was able to test
> > the series with "git am -3" to get around a merge issue on
> > perf-tools-next.
> >
> > Reviewed-by: Ian Rogers <irogers@google.com>
> > Tested-by: Ian Rogers <irogers@google.com>
> >
>
> Thank you for following this series and providing many valuable suggestions.

It's not applied cleanly.  Can you please rebase onto the current
tmp.perf-tools-next branch in the following tree?

  git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git

Thanks,
Namhyung

  reply	other threads:[~2023-09-27  1:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25  5:57 [PATCH v10 0/7] Add metrics for Arm CMN Jing Zhang
2023-09-25  5:57 ` [PATCH v10 1/7] perf pmu: "Compat" supports regular expression matching identifiers Jing Zhang
2023-09-25  5:57 ` [PATCH v10 2/7] perf metric: " Jing Zhang
2023-09-25  5:57 ` [PATCH v10 3/7] perf jevents: Support EventidCode and NodeType Jing Zhang
2023-09-25  5:57 ` [PATCH v10 4/7] perf test: Make matching_pmu effective Jing Zhang
2023-09-25  5:57 ` [PATCH v10 5/7] perf test: Add pmu-event test for "Compat" and new event_field Jing Zhang
2023-09-25  5:57 ` [PATCH v10 6/7] perf jevents: Add support for Arm CMN PMU aliasing Jing Zhang
2023-09-25  5:57 ` [PATCH v10 7/7] perf vendor events: Add JSON metrics for Arm CMN Jing Zhang
2023-09-25 16:37 ` [PATCH v10 0/7] Add " Ian Rogers
2023-09-26  3:15   ` Jing Zhang
2023-09-27  1:00     ` Namhyung Kim [this message]
2023-09-27  6:06       ` Jing Zhang
2023-09-28  4:00         ` Namhyung Kim

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=CAM9d7cjjSJybJEbSdBkVH3qx7RDqriv4tqBCNw1Yi9bAeUf3Yw@mail.gmail.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mike.leach@linaro.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=renyu.zj@linux.alibaba.com \
    --cc=will@kernel.org \
    --cc=xueshuai@linux.alibaba.com \
    --cc=zhuo.song@linux.alibaba.com \
    /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).