From: Andrew Murray <andrew.murray@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 2/2] perf: Use consistent style of comments for optional callbacks
Date: Fri, 3 May 2019 11:23:15 +0100 [thread overview]
Message-ID: <20190503102315.5697-3-andrew.murray@arm.com> (raw)
In-Reply-To: <20190503102315.5697-1-andrew.murray@arm.com>
To improve the readability of perf_event.h, let's be consistent in how we
annotate optional struct pmu callbacks. Where a multi-line comment block
is present before a single function prototype we add the annotation at the
end of the block. Otherwise we use a single line comment at the end of the
function prototype.
Signed-off-by: Andrew Murray <andrew.murray@arm.com>
---
include/linux/perf_event.h | 25 ++++++++++++++++++-------
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
index 27c1cb3cddf1..f0479c99d2ec 100644
--- a/include/linux/perf_event.h
+++ b/include/linux/perf_event.h
@@ -393,8 +393,10 @@ struct pmu {
/*
* Will return the value for perf_event_mmap_page::index for this event,
* if no implementation is provided it will default to: 0.
+ *
+ * Optional.
*/
- int (*event_idx) (struct perf_event *event); /*optional */
+ int (*event_idx) (struct perf_event *event);
/*
* context-switches callback
@@ -409,15 +411,18 @@ struct pmu {
/*
* Set up pmu-private data structures for an AUX area
+ *
+ * Optional.
*/
void *(*setup_aux) (struct perf_event *event, void **pages,
int nr_pages, bool overwrite);
- /* optional */
/*
* Free pmu-private AUX data structures
+ *
+ * Optional.
*/
- void (*free_aux) (void *aux); /* optional */
+ void (*free_aux) (void *aux);
/*
* Validate address range filters: make sure the HW supports the
@@ -426,9 +431,10 @@ struct pmu {
*
* Runs in the context of the ioctl()ing process and is not serialized
* with the rest of the PMU callbacks.
+ *
+ * Optional.
*/
int (*addr_filters_validate) (struct list_head *filters);
- /* optional */
/*
* Synchronize address range filter configuration:
@@ -440,19 +446,24 @@ struct pmu {
*
* May (and should) traverse event::addr_filters::list, for which its
* caller provides necessary serialization.
+ *
+ * Optional.
*/
void (*addr_filters_sync) (struct perf_event *event);
- /* optional */
/*
* Filter events for PMU-specific reasons.
+ *
+ * Optional.
*/
- int (*filter_match) (struct perf_event *event); /* optional */
+ int (*filter_match) (struct perf_event *event);
/*
* Check period value for PERF_EVENT_IOC_PERIOD ioctl.
+ *
+ * Optional.
*/
- int (*check_period) (struct perf_event *event, u64 value); /* optional */
+ int (*check_period) (struct perf_event *event, u64 value);
};
enum perf_addr_filter_action_t {
--
2.21.0
prev parent reply other threads:[~2019-05-03 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 10:23 [PATCH v1 0/2] perf: Minor typo and style changes to perf_event.h Andrew Murray
2019-05-03 10:23 ` [PATCH v1 1/2] perf: Fix incorrect comment for event_idx callback Andrew Murray
2019-05-03 10:23 ` Andrew Murray [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=20190503102315.5697-3-andrew.murray@arm.com \
--to=andrew.murray@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®