* Vince Weaver <vi...@deater.net> wrote:
> On Wed, 25 Feb 2015, tip-bot for Matt Fleming wrote:
>
> > diff --git a/include/uapi/linux/perf_event.h
> > b/include/uapi/linux/perf_event.h
> > index 1e3cd07..3c8b45d 100644
> > --- a/include/uapi/linux/perf_event.h
> > +++ b/include/uapi/linux/perf_event.h
> > @@ -32,6 +32,7 @@ enum perf_type_id {
> > PERF_TYPE_HW_CACHE = 3,
> > PERF_TYPE_RAW = 4,
> > PERF_TYPE_BREAKPOINT = 5,
> > + PERF_TYPE_INTEL_CQM = 6,
> >
> > PERF_TYPE_MAX, /* non-ABI */
> > };
>
> I thought the rule was no adding support for things in perf_event unless
> they were sufficiently generic as to be cross-architecture.
>
> Having a high-level event type with "intel" in the name seems awfully
> specific.
That's a fair point. Peter?
Thanks,
Ingo
--
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/
