mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: "Peter Zijlstra" <peterz@infradead.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Arnaldo Carvalho de Melo" <acme@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>,
	"John Garry" <john.g.garry@oracle.com>,
	"Will Deacon" <will@kernel.org>,
	"James Clark" <james.clark@linaro.org>,
	"Mike Leach" <mike.leach@linaro.org>,
	"Leo Yan" <leo.yan@linux.dev>,
	"Weilin Wang" <weilin.wang@intel.com>,
	"Ravi Bangoria" <ravi.bangoria@amd.com>,
	"Sandipan Das" <sandipan.das@amd.com>,
	"Xu Yang" <xu.yang_2@nxp.com>,
	"Benjamin Gray" <bgray@linux.ibm.com>,
	"Athira Jajeev" <atrajeev@linux.vnet.ibm.com>,
	"Howard Chu" <howardchu95@gmail.com>,
	"Veronika Molnarova" <vmolnaro@redhat.com>,
	"Dr. David Alan Gilbert" <linux@treblig.org>,
	"Oliver Upton" <oliver.upton@linux.dev>,
	"Changbin Du" <changbin.du@huawei.com>,
	"Steinar H. Gunderson" <sesse@google.com>,
	"Ze Gao" <zegao2021@gmail.com>,
	"Dominique Martinet" <asmadeus@codewreck.org>,
	"Clément Le Goffic" <clement.legoffic@foss.st.com>,
	"Sun Haiyong" <sunhaiyong@loongson.cn>,
	"Junhao He" <hejunhao3@huawei.com>,
	"Tiezhu Yang" <yangtiezhu@loongson.cn>,
	"Yicong Yang" <yangyicong@hisilicon.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Ian Rogers" <irogers@google.com>
Subject: Re: (subset) [PATCH v3 00/13] Tool and hwmon PMUs
Date: Mon, 14 Oct 2024 09:57:44 -0700	[thread overview]
Message-ID: <172892501876.15689.3033776452114241279.b4-ty@kernel.org> (raw)
In-Reply-To: <20241002032016.333748-1-irogers@google.com>


On Tue, 01 Oct 2024 20:20:03 -0700, Ian Rogers wrote:
> Rather than have fake and tool PMUs being special flags in an evsel,
> create special PMUs. This allows, for example, duration_time to also
> be tool/duration_time/. Once adding events to the tools PMU is just
> adding to an array, add events for nearly all the expr literals like
> num_cpus_online. Rather than create custom logic for finding and
> describing the tool events use json and add a notion of common json
> for the tool events.
> 
> [...]

Applied patch 1-10 to perf-tools-next, thanks!

Best regards,
Namhyung

      parent reply	other threads:[~2024-10-14 16:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02  3:20 Ian Rogers
2024-10-02  3:20 ` [PATCH v3 01/13] perf pmu: Simplify an asprintf error message Ian Rogers
2024-10-02  3:20 ` [PATCH v3 02/13] perf pmu: Allow hardcoded terms to be applied to attributes Ian Rogers
2024-10-02  3:20 ` [PATCH v3 03/13] perf parse-events: Expose/rename config_term_name Ian Rogers
2024-10-02  3:20 ` [PATCH v3 04/13] perf tool_pmu: Factor tool events into their own PMU Ian Rogers
2024-10-02  3:20 ` [PATCH v3 05/13] perf tool_pmu: Rename enum perf_tool_event to tool_pmu_event Ian Rogers
2024-10-02  3:20 ` [PATCH v3 06/13] perf tool_pmu: Rename perf_tool_event__* to tool_pmu__* Ian Rogers
2024-10-02  3:20 ` [PATCH v3 07/13] perf tool_pmu: Move expr literals to tool_pmu Ian Rogers
2024-10-02  3:20 ` [PATCH v3 08/13] perf jevents: Add tool event json under a common architecture Ian Rogers
2024-10-02  3:20 ` [PATCH v3 09/13] perf tool_pmu: Switch to standard pmu functions and json descriptions Ian Rogers
2024-10-02  3:20 ` [PATCH v3 10/13] perf tests: Add tool PMU test Ian Rogers
2024-10-02  3:20 ` [PATCH v3 11/13] perf hwmon_pmu: Add a tool PMU exposing events from hwmon in sysfs Ian Rogers
2024-10-02  3:20 ` [PATCH v3 12/13] perf test: Add hwmon "PMU" test Ian Rogers
2024-10-02  3:20 ` [PATCH v3 13/13] perf docs: Document tool and hwmon events Ian Rogers
2024-10-14 16:57 ` Namhyung Kim [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=172892501876.15689.3033776452114241279.b4-ty@kernel.org \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=asmadeus@codewreck.org \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=bgray@linux.ibm.com \
    --cc=changbin.du@huawei.com \
    --cc=clement.legoffic@foss.st.com \
    --cc=hejunhao3@huawei.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=john.g.garry@oracle.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=leo.yan@linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=mark.rutland@arm.com \
    --cc=mike.leach@linaro.org \
    --cc=mingo@redhat.com \
    --cc=oliver.upton@linux.dev \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.com \
    --cc=sandipan.das@amd.com \
    --cc=sesse@google.com \
    --cc=sunhaiyong@loongson.cn \
    --cc=vmolnaro@redhat.com \
    --cc=weilin.wang@intel.com \
    --cc=will@kernel.org \
    --cc=xu.yang_2@nxp.com \
    --cc=yangtiezhu@loongson.cn \
    --cc=yangyicong@hisilicon.com \
    --cc=zegao2021@gmail.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

all inboxes | Powered by JetHome®