Add PMU_RANGE_ATTR() and PMU_RANGE_RESV() (for reserved areas) which
generate functions to extract the relevent bits from
event->attr.config{,1,2} for use by sw-like pmus where the
'config{,1,2}' values don't map directly to hardware registers.

Signed-off-by: Cody P Schafer <c...@linux.vnet.ibm.com>
---
 include/linux/perf_event.h | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
index e56b07f..2702e91 100644
--- a/include/linux/perf_event.h
+++ b/include/linux/perf_event.h
@@ -871,4 +871,21 @@ _name##_show(struct device *dev,                           
        \
                                                                        \
 static struct device_attribute format_attr_##_name = __ATTR_RO(_name)
 
+#define PMU_RANGE_ATTR(name, attr_var, bit_start, bit_end)             \
+PMU_FORMAT_ATTR(name, #attr_var ":" #bit_start "-" #bit_end);          \
+PMU_RANGE_RESV(name, attr_var, bit_start, bit_end)
+
+#define PMU_RANGE_RESV(name, attr_var, bit_start, bit_end)             \
+static u64 event_get_##name##_max(void)                                        
\
+{                                                                      \
+       int bits = (bit_end) - (bit_start) + 1;                         \
+       return ((0x1ULL << (bits - 1ULL)) - 1ULL) |                     \
+               (0xFULL << (bits - 4ULL));                              \
+}                                                                      \
+static u64 event_get_##name(struct perf_event *event)                  \
+{                                                                      \
+       return (event->attr.attr_var >> (bit_start)) &                  \
+               event_get_##name##_max();                               \
+}
+
 #endif /* _LINUX_PERF_EVENT_H */
-- 
1.8.5.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to