On Mon, 9 Feb 2015 21:47:42 -0800 Alexei Starovoitov <ast@xxxxxxxxxxxx> wrote: > On Mon, Feb 9, 2015 at 9:45 PM, Alexei Starovoitov <ast@xxxxxxxxxxxx> wrote: > > I thought we already stated that. > > Here is the quote from perf_event.h: > > * # The RAW record below is opaque data wrt the ABI > > * # > > * # That is, the ABI doesn't make any promises wrt to > > * # the stability of its content, it may vary depending > > * # on event, hardware, kernel version and phase of > > * # the moon. > > * # > > * # In other words, PERF_SAMPLE_RAW contents are not an ABI. > > > > and this example is reading PERF_SAMPLE_RAW events and > > uses locally defined structs to print them for simplicity. > > to underline my point once more: > addition of bpf doesn't change at all what PERF_SAMPLE_RAW already > delivers to user space. > so no new ABIs anywhere. Again, it we give an example of how to hard code the data, definitely expect this to show up in user space. Users are going to look at this code to learn how to use eBPF. I really want it to do it the correct way instead of the 'easy' way. Because whatever way we have it here, will be the way we will see it out in the wild. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
