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: kan.liang@linux.intel.com, jolsa@kernel.org, namhyung@kernel.org,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	artem.bityutskiy@linux.intel.com, andi.kleen@intel.com
Subject: Re: [PATCH] perf vendor events intel: Add Emerald Rapids
Date: Thu, 19 Jan 2023 09:56:15 -0300	[thread overview]
Message-ID: <Y8k974RqTSIle9ZQ@kernel.org> (raw)
In-Reply-To: <CAP-5=fWMPYmofTL262HQB1jOiqRD5dKtAhaWrBbT-vq-NYsXcg@mail.gmail.com>

Em Wed, Jan 18, 2023 at 10:02:04AM -0800, Ian Rogers escreveu:
> On Wed, Jan 18, 2023 at 9:57 AM <kan.liang@linux.intel.com> wrote:
> >
> > From: Kan Liang <kan.liang@linux.intel.com>
> >
> > The event list of the Emerald Rapids is the same as the Sapphire
> > Rapids. Add the CPU model ID of Emerald Rapids into the mapfile.csv and
> > point it to the event list of Sapphire Rapids.
> >
> > Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
> 
> Acked-by: Ian Rogers <irogers@google.com>
> 
> I note it currently isn't on the perfmon github:
> https://github.com/intel/perfmon/blob/main/mapfile.csv
> This will create a diff from the version of mapfile.csv generated by:
> https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
> Presumably there will be an update to solve that.

Thanks, applied.

- Arnaldo


      parent reply	other threads:[~2023-01-19 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 17:56 [PATCH] perf vendor events intel: Add Emerald Rapids kan.liang
2023-01-18 18:02 ` Ian Rogers
2023-01-18 20:14   ` Liang, Kan
2023-01-19 12:56   ` 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=Y8k974RqTSIle9ZQ@kernel.org \
    --to=acme@kernel.org \
    --cc=andi.kleen@intel.com \
    --cc=artem.bityutskiy@linux.intel.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=namhyung@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 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.