From: Alexander Antonov <alexander.antonov@linux.intel.com>
To: acme@kernel.org
Cc: linux-kernel@vger.kernel.org, jolsa@redhat.com,
alexander.shishkin@linux.intel.com, mark.rutland@arm.com,
namhyung@kernel.org, mingo@redhat.com, peterz@infradead.org,
ak@linux.intel.com, alexander.antonov@linux.intel.com
Subject: [PATCH 2/5] perf evsel: Introduce an observed performance device
Date: Thu, 10 Dec 2020 12:03:37 +0300 [thread overview]
Message-ID: <20201210090340.14358-3-alexander.antonov@linux.intel.com> (raw)
In-Reply-To: <20201210090340.14358-1-alexander.antonov@linux.intel.com>
Adding evsel::perf_device void pointer.
For performance monitoring purposes, an evsel can have a related device.
These changes allow to attribute, for example, I/O performance metrics
to IIO stack.
Signed-off-by: Alexander Antonov <alexander.antonov@linux.intel.com>
---
tools/perf/util/evsel.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/util/evsel.h b/tools/perf/util/evsel.h
index 79a860d8e3ee..c346920f477a 100644
--- a/tools/perf/util/evsel.h
+++ b/tools/perf/util/evsel.h
@@ -127,6 +127,7 @@ struct evsel {
* See also evsel__has_callchain().
*/
__u64 synth_sample_type;
+ void *perf_device;
};
struct perf_missing_features {
--
2.19.1
next prev parent reply other threads:[~2020-12-10 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 9:03 [PATCH 0/5] perf stat: Introduce --iiostat mode to provide I/O performance metrics Alexander Antonov
2020-12-10 9:03 ` [PATCH 1/5] perf stat: Add AGGR_IIO_STACK mode Alexander Antonov
2020-12-10 9:03 ` Alexander Antonov [this message]
2020-12-10 9:03 ` [PATCH 3/5] perf stat: Basic support for iiostat in perf stat Alexander Antonov
2020-12-10 9:03 ` [PATCH 4/5] perf stat: Helper functions for IIO stacks list in iiostat mode Alexander Antonov
2020-12-10 9:03 ` [PATCH 5/5] perf stat: Enable --iiostat mode for x86 platforms Alexander Antonov
2020-12-14 13:28 ` [PATCH 0/5] perf stat: Introduce --iiostat mode to provide I/O performance metrics Arnaldo Carvalho de Melo
2020-12-15 3:04 ` Andi Kleen
2020-12-15 13:58 ` Arnaldo Carvalho de Melo
2020-12-20 17:23 ` Alexander Antonov
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=20201210090340.14358-3-alexander.antonov@linux.intel.com \
--to=alexander.antonov@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox