public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>, 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>,
	Zhengjun Xing <zhengjun.xing@linux.intel.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Edward Baker <edward.baker@intel.com>,
	Perry Taylor <perry.taylor@intel.com>,
	Caleb Biggers <caleb.biggers@intel.com>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v3 00/21] Update uncore topics, 1x event updates, 2x new archs.
Date: Fri, 14 Apr 2023 10:18:16 +0200	[thread overview]
Message-ID: <20230414081816.GS4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <ZDgL1Qca7N+Wilm6@kernel.org>

On Thu, Apr 13, 2023 at 11:04:05AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Apr 13, 2023 at 06:29:28AM -0700, Ian Rogers escreveu:
> > Update the uncore PMUs and topic classification as created by:
> > https://github.com/intel/perfmon/pull/70
> > 
> > Event updates stem from:
> > https://github.com/intel/perfmon/pull/68
> > impacting alderlake, icelakex and sapphirerapids.
> > 
> > Grand Ridge and Sierra Forest events stem from:
> > https://github.com/intel/perfmon/pull/69
> > 
> > Changes generated by with PR70 in place:
> > https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
> > 
> > v3. Rebase over the update of alderlake and icelakex events.
> > v2. Adds improvements to uncore topics, uncore PMU name fixes and
> >     fixes a trigraph issue from ??? being in the json.
> 
> b4 isn't liking it:

Fwiw, the way I've set up b4 it takes the patches from my local
mailstore and it doesn't matter what made it out to lkml. Specifically,
I pipe the patches from mutt directly into b4.

I think there's some information in the b4 docs on how to set that up,
but let me know if you want more info.

  parent reply	other threads:[~2023-04-14  8:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 13:29 [PATCH v3 00/21] Update uncore topics, 1x event updates, 2x new archs Ian Rogers
2023-04-13 13:29 ` [PATCH v3 01/21] perf vendor events intel: Update sapphirerapids to v1.12 Ian Rogers
2023-04-13 13:29 ` [PATCH v3 02/21] perf vendor events intel: Add grandridge Ian Rogers
2023-04-13 13:29 ` [PATCH v3 03/21] perf vendor events intel: Add sierraforest Ian Rogers
2023-04-13 13:29 ` [PATCH v3 04/21] perf vendor events intel: Fix uncore topics for alderlake Ian Rogers
2023-04-13 13:29 ` [PATCH v3 05/21] perf vendor events intel: Fix uncore topics for broadwell Ian Rogers
2023-04-13 13:29 ` [PATCH v3 06/21] perf vendor events intel: Fix uncore topics for broadwellde Ian Rogers
2023-04-13 13:29 ` [PATCH v3 07/21] perf vendor events intel: Fix uncore topics for broadwellx Ian Rogers
2023-04-13 13:29 ` [PATCH v3 08/21] perf vendor events intel: Fix uncore topics for cascadelakex Ian Rogers
2023-04-13 13:29 ` [PATCH v3 09/21] perf vendor events intel: Fix uncore topics for haswell Ian Rogers
2023-04-13 13:29 ` [PATCH v3 10/21] perf vendor events intel: Fix uncore topics for haswellx Ian Rogers
2023-04-13 13:29 ` [PATCH v3 11/21] perf vendor events intel: Fix uncore topics for icelake Ian Rogers
2023-04-13 13:29 ` [PATCH v3 12/21] perf vendor events intel: Fix uncore topics for icelakex Ian Rogers
2023-04-13 13:29 ` [PATCH v3 13/21] perf vendor events intel: Fix uncore topics for ivybridge Ian Rogers
2023-04-13 13:29 ` [PATCH v3 14/21] perf vendor events intel: Fix uncore topics for ivytown Ian Rogers
2023-04-13 13:29 ` [PATCH v3 15/21] perf vendor events intel: Fix uncore topics for jaketown Ian Rogers
2023-04-13 13:29 ` [PATCH v3 16/21] perf vendor events intel: Fix uncore topics for knightslanding Ian Rogers
2023-04-13 13:29 ` [PATCH v3 17/21] perf vendor events intel: Fix uncore topics for sandybridge Ian Rogers
2023-04-13 13:29 ` [PATCH v3 18/21] perf vendor events intel: Fix uncore topics for skylake Ian Rogers
2023-04-13 13:29 ` [PATCH v3 19/21] perf vendor events intel: Fix uncore topics for skylakex Ian Rogers
2023-04-13 13:29 ` [PATCH v3 20/21] perf vendor events intel: Fix uncore topics for snowridgex Ian Rogers
2023-04-13 13:29 ` [PATCH v3 21/21] perf vendor events intel: Fix uncore topics for tigerlake Ian Rogers
2023-04-13 14:04 ` [PATCH v3 00/21] Update uncore topics, 1x event updates, 2x new archs Arnaldo Carvalho de Melo
2023-04-13 15:34   ` Ian Rogers
2023-04-14  8:18   ` Peter Zijlstra [this message]
2023-04-14 23:14     ` Ian Rogers
2023-04-15  0:07       ` Arnaldo Carvalho de Melo
2023-04-13 21:57 ` Arnaldo Carvalho de Melo

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=20230414081816.GS4253@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=caleb.biggers@intel.com \
    --cc=edward.baker@intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.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=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