Re: [PATCH 1/6] perf_counter: move the event overflow output bits to record_type

[Corey Ashford <cjashfor@linux.vnet.ibm.com>]

Peter Zijlstra wrote:
> Per suggestion from Paul, move the event overflow bits to record_type
> and sanitize the enums a bit.
> 
> Breaks the ABI -- again ;-)
> 
[snip]

With this patch, the definitions look like this now:

[snip]
/*
  * Bits that can be set in hw_event.record_type to request information
  * in the overflow packets.
  */
enum perf_counter_record_format {
         PERF_RECORD_IP          = 1U << 0,
         PERF_RECORD_TID         = 1U << 1,
         PERF_RECORD_GROUP       = 1U << 2,
         PERF_RECORD_CALLCHAIN   = 1U << 3,
};

[snip]
enum perf_event_type {

         PERF_EVENT_MMAP                 = 1,
         PERF_EVENT_MUNMAP               = 2,

         /*
          * Half the event type space is reserved for the counter overflow
          * bitfields, as found in hw_event.record_type.
          *
          * These events will have types of the form:
          *   PERF_EVENT_COUNTER_OVERFLOW { | __PERF_EVENT_* } *
          */
         PERF_EVENT_COUNTER_OVERFLOW     = 1UL << 31,
         __PERF_EVENT_IP                 = PERF_RECORD_IP,
         __PERF_EVENT_TID                = PERF_RECORD_TID,
         __PERF_EVENT_GROUP              = PERF_RECORD_GROUP,
         __PERF_EVENT_CALLCHAIN          = PERF_RECORD_CALLCHAIN,
};
[snip]


Unless I'm misreading something here, there's overlap in the enum values 
of perf_event_type enum. PERF_EVENT_MMAP has the same value as 
__PERF_EVENT_IP, and PERF_EVENT_MUNMAP has the same value as 
__PERF_EVENT_TID.

Are these lower bits being reused when PERF_EVENT_COUNTER_OVERFLOW is 
OR'd in, which would imply that PERF_EVENT_MMAP and PERF_EVENT_MUNMAP 
are mutually exclusive with all of the PERF_EVENT_COUNTER_OVERFLOW values.

Actually, I don't really understand the purpose of the PERF_EVENT_MMAP 
and PERF_EVENT_MUNMAP bits. My hazy understanding is that they are used 
for finding the file, function and line number at overflow interrupt 
time, but it's unclear to me what that has to do with mmap.  I'll go 
back and try to find the relevant patch notes again.

- Corey