From: Tim Blechmann <tim@klingt.org>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] perf: replace record_type with sample_type in design document
Date: Mon, 28 Dec 2009 12:20:16 +0100 [thread overview]
Message-ID: <4B389470.6070209@klingt.org> (raw)
In-Reply-To: <2ba0ea41a0372f31fcebda030440a55d37beeefb.1261999187.git.tim@klingt.org>
[-- Attachment #1.1: Type: text/plain, Size: 340 bytes --]
perf_event_attr.record_type has been renamed to sample_type,
perf_event_record_format with perf_event_sample_format. the design
document was still using the old name.
Signed-off-by: Tim Blechmann <tim@klingt.org>
---
tools/perf/design.txt | 25 +++++++++++++++----------
1 files changed, 15 insertions(+), 10 deletions(-)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0002-perf-replace-record_type-with-sample_type-in-design-.patch --]
[-- Type: text/x-patch; name="0002-perf-replace-record_type-with-sample_type-in-design-.patch", Size: 1989 bytes --]
diff --git a/tools/perf/design.txt b/tools/perf/design.txt
index d68515f..567a041 100644
--- a/tools/perf/design.txt
+++ b/tools/perf/design.txt
@@ -48,7 +48,7 @@ struct perf_event_attr {
__u64 sample_freq;
};
- __u32 record_type;
+ __u32 sample_type;
__u32 read_format;
__u64 disabled : 1, /* off by default */
@@ -175,20 +175,25 @@ into account.
A "sampling" counter is one that is set up to generate an interrupt
every N events, where N is given by 'sample_period'. A sampling counter
-has sample_period > 0. The record_type controls what data is recorded on each
+has sample_period > 0. The sample_type controls what data is recorded on each
interrupt:
/*
- * Bits that can be set in hw_event.record_type to request information
+ * Bits that can be set in hw_event.sample_type to request information
* in the overflow packets.
*/
-enum perf_event_record_format {
- PERF_RECORD_IP = 1U << 0,
- PERF_RECORD_TID = 1U << 1,
- PERF_RECORD_TIME = 1U << 2,
- PERF_RECORD_ADDR = 1U << 3,
- PERF_RECORD_GROUP = 1U << 4,
- PERF_RECORD_CALLCHAIN = 1U << 5,
+enum perf_event_sample_format {
+ PERF_SAMPLE_IP = 1U << 0,
+ PERF_SAMPLE_TID = 1U << 1,
+ PERF_SAMPLE_TIME = 1U << 2,
+ PERF_SAMPLE_ADDR = 1U << 3,
+ PERF_SAMPLE_READ = 1U << 4,
+ PERF_SAMPLE_CALLCHAIN = 1U << 5,
+ PERF_SAMPLE_ID = 1U << 6,
+ PERF_SAMPLE_CPU = 1U << 7,
+ PERF_SAMPLE_PERIOD = 1U << 8,
+ PERF_SAMPLE_STREAM_ID = 1U << 9,
+ PERF_SAMPLE_RAW = 1U << 10,
};
Such (and other) events will be recorded in a ring-buffer, which is
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
parent reply other threads:[~2009-12-28 11:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2ba0ea41a0372f31fcebda030440a55d37beeefb.1261999187.git.tim@klingt.org>]
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=4B389470.6070209@klingt.org \
--to=tim@klingt.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox