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: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1] perf jevents: Add cpuid to model lookup command
Date: Wed, 4 Sep 2024 10:47:31 -0300	[thread overview]
Message-ID: <Zthk895rlxYbUbMl@x1> (raw)
In-Reply-To: <20240904044351.712080-1-irogers@google.com>

On Tue, Sep 03, 2024 at 09:43:51PM -0700, Ian Rogers wrote:
> When restricting jevents generated json lookup code with JEVENTS_MODEL
> a list of models must be provided. Some builds don't know model names
> but know cpuids. Add a command that can convert a cpuid to a model
> using mapfile.csv files. This can be used with JEVENTS_MODEL like:
> 
> ```
> $ make JEVENTS_MODEL=`./pmu-events/models.py x86 'GenuineIntel-6-8D-1,AuthenticAMD-26-1' pmu-events/arch/`
> ```

thanks, applied, added:

  Committer testing:
  
    $ tools/perf/pmu-events/models.py x86 'GenuineIntel-6-8D-1,AuthenticAMD-26-1' tools/perf/pmu-events/arch/
    tigerlake,amdzen5
    $ perf stat -v sleep 1 |& head -1
    Using CPUID GenuineIntel-6-B7-1
    $ tools/perf/pmu-events/models.py x86 'GenuineIntel-6-B7-1' tools/perf/pmu-events/arch/
    alderlake
    $
  
  Signed-off-by: Ian Rogers <irogers@google.com>
  Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>

- Arnaldo

      reply	other threads:[~2024-09-04 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04  4:43 [PATCH v1] perf jevents: Add cpuid to model lookup command Ian Rogers
2024-09-04 13:47 ` 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=Zthk895rlxYbUbMl@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@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=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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.