[PATCH] perf: rename perf_event_hw_event in design document

From: Tim Blechmann
Date: Sun Dec 27 2009 - 08:43:26 EST



perf_event_hw_event has been renamed to perf_event_attr. the design
document was still using the old name, though.

Signed-off-by: Tim Blechmann <tim@xxxxxxxxxx>
---
tools/perf/design.txt | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)


diff --git a/tools/perf/design.txt b/tools/perf/design.txt
index fdd42a8..a58cc9a 100644
--- a/tools/perf/design.txt
+++ b/tools/perf/design.txt
@@ -21,7 +21,7 @@ There's one file descriptor per virtual counter used.
The special file descriptor is opened via the perf_event_open()
system call:

- int sys_perf_event_open(struct perf_event_hw_event *hw_event_uptr,
+ int sys_perf_event_open(struct perf_event_attr *hw_event_uptr,
pid_t pid, int cpu, int group_fd,
unsigned long flags);

@@ -32,9 +32,9 @@ can be used to set the blocking mode, etc.
Multiple counters can be kept open at a time, and the counters
can be poll()ed.

-When creating a new counter fd, 'perf_event_hw_event' is:
+When creating a new counter fd, 'perf_event_attr' is:

-struct perf_event_hw_event {
+struct perf_event_attr {
/*
* The MSB of the config word signifies if the rest contains cpu
* specific (raw) counter configuration data, if unset, the next
@@ -397,7 +397,7 @@ Notification of new events is possible through poll()/select()/epoll() and
fcntl() managing signals.

Normally a notification is generated for every page filled, however one can
-additionally set perf_event_hw_event.wakeup_events to generate one every
+additionally set perf_event_attr.wakeup_events to generate one every
so many counter overflow events.

Future work will include a splice() interface to the ring-buffer.

Attachment: signature.asc
Description: OpenPGP digital signature