All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: zhengjun.xing@linux.intel.com, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@intel.com, jolsa@redhat.com,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	adrian.hunter@intel.com, ak@linux.intel.com,
	kan.liang@linux.intel.com
Subject: Re: [PATCH v2 1/2] perf vendor events intel: Add metrics for Sapphirerapids
Date: Fri, 3 Jun 2022 21:46:07 +0200	[thread overview]
Message-ID: <Yppk/4/d3s5tiO6T@kernel.org> (raw)
In-Reply-To: <CAP-5=fUpmtWRYcZQoV26q4ZCGVmORJpTe_Mz3Y=JmH3tXLvapw@mail.gmail.com>

Em Wed, Jun 01, 2022 at 05:56:24PM -0700, Ian Rogers escreveu:
> On Sat, May 28, 2022 at 2:59 AM <zhengjun.xing@linux.intel.com> wrote:
> >
> > From: Zhengjun Xing <zhengjun.xing@linux.intel.com>
> >
> > Add JSON metrics for Sapphirerapids to perf.
> >
> > Based on TMA4.4 metrics.
> >
> > https://download.01.org/perfmon/TMA_Metrics-full.csv
> >
> > Signed-off-by: Zhengjun Xing <zhengjun.xing@linux.intel.com>
> 
> I didn't find a sapphirerapids to test this on, but non-CPU specific
> event/metric tests passed.
> 
> Tested-by: Ian Rogers <irogers@google.com>

Thanks, applied both.

- Arnaldo


      reply	other threads:[~2022-06-03 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28  9:59 [PATCH v2 1/2] perf vendor events intel: Add metrics for Sapphirerapids zhengjun.xing
2022-05-28  9:59 ` [PATCH v2 2/2] perf vendor events intel: Update metrics for Alderlake zhengjun.xing
2022-06-02  0:54   ` Ian Rogers
2022-06-02  0:56 ` [PATCH v2 1/2] perf vendor events intel: Add metrics for Sapphirerapids Ian Rogers
2022-06-03 19:46   ` 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=Yppk/4/d3s5tiO6T@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.