linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>
Cc: 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>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Xing Zhengjun <zhengjun.xing@linux.intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	John Garry <john.g.garry@oracle.com>,
	Stephane Eranian <eranian@google.com>,
	Perry Taylor <perry.taylor@intel.com>,
	Caleb Biggers <caleb.biggers@intel.com>
Subject: Re: [PATCH v1 00/32] Refresh Intel vendor events
Date: Wed, 21 Dec 2022 13:52:52 -0300	[thread overview]
Message-ID: <Y6M55I/gDRBAfPvc@kernel.org> (raw)
In-Reply-To: <Y6M0zwN+1yovTeZH@kernel.org>

Em Wed, Dec 21, 2022 at 01:31:11PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Dec 15, 2022 at 12:23:14PM -0500, Liang, Kan escreveu:
> > On 2022-12-15 1:47 a.m., Ian Rogers wrote:
> > > Use new repository [1] and converter script to regenerate Intel vendor
> > > metrics. In particular this change removes unnecessary json fields and
> > > correct uncore events that previously had a buggy converter.

> > Thanks Ian.

> > The patch series looks good to me.

> > Acked-by: Kan Liang <kan.liang@linux.intel.com>

> b4 doesn't like it, I'll apply it manually, probably some went over
> message size limits?

Had to adjust the first one manually due, IIRC, to the hashmap changes
that went upstream via the bpf tree, then use b4 3 times, cherrypicking
ranges of the series to get all merged.

Ian, please check what happened so that this isn't this manual next
time.

- Arnaldo

      reply	other threads:[~2022-12-21 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  6:47 [PATCH v1 00/32] Refresh Intel vendor events Ian Rogers
2022-12-15  6:47 ` [PATCH v1 01/32] perf test pmu-events: Fake PMU metric workaround Ian Rogers
2022-12-15  6:47 ` [PATCH v1 02/32] perf vendor events intel: Refresh alderlake metrics Ian Rogers
2022-12-15  6:47 ` [PATCH v1 03/32] perf vendor events intel: Refresh alderlake-n metrics Ian Rogers
2022-12-15  6:47 ` [PATCH v1 04/32] perf vendor events intel: Refresh bonnell events Ian Rogers
2022-12-15 17:23 ` [PATCH v1 00/32] Refresh Intel vendor events Liang, Kan
2022-12-21 16:31   ` Arnaldo Carvalho de Melo
2022-12-21 16:52     ` 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=Y6M55I/gDRBAfPvc@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=caleb.biggers@intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --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=perry.taylor@intel.com \
    --cc=peterz@infradead.org \
    --cc=zhengjun.xing@linux.intel.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).