perf: rename perf_event_hw_event in design document
PATCH 1/1 perf: rename perf_event_hw_event in design document
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 <[email protected]>
--- tools/perf/design.txt | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-)
tools/perf/design.txt +4 -4
@@ -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.
[tip:perf/urgent] perf: Rename perf_event_hw_event in design document
Commit-ID: 0b413e44d64aeac36a096505a40fc2ff470872fa Gitweb: http://git.kernel.org/tip/0b413e44d64aeac36a096505a40fc2ff470872fa Author: Tim Blechmann <[email protected]> AuthorDate: Sun, 27 Dec 2009 14:43:06 +0100 Committer: Ingo Molnar <[email protected]> CommitDate: Mon, 28 Dec 2009 09:14:37 +0100
perf: Rename perf_event_hw_event in design document
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 <[email protected]>
Cc Peter Zijlstra <[email protected]>
Cc Mike Galbraith <[email protected]>
Cc Paul Mackerras <[email protected]>
Cc Arnaldo Carvalho de Melo <[email protected]>
Cc Frederic Weisbecker <[email protected]>
LKML-Reference: <[email protected]>
Signed-off-by Ingo Molnar <[email protected]>
--- tools/perf/design.txt | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-)
tools/perf/design.txt +4 -4
@@ -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
@@ -399,7 +399,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.