[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200724144632.GE1180481@tassilo.jf.intel.com>
Date: Fri, 24 Jul 2020 07:46:32 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: "Liang, Kan" <kan.liang@...ux.intel.com>, acme@...hat.com,
mingo@...nel.org, linux-kernel@...r.kernel.org, jolsa@...nel.org,
eranian@...gle.com, alexander.shishkin@...ux.intel.com,
like.xu@...ux.intel.com
Subject: Re: [PATCH V7 07/14] perf/core: Add a new PERF_EV_CAP_COEXIST event
capability
> Something that seems to 'work' is:
> '{cycles,cpu/instructions,period=50000/}', so maybe you can make the
> group modifier :S use any sampling event if there is one, and otherwise
> designate the leader.
>
> Then you can write things like:
>
> '{slots, metric1, metric2, cpu/cycles,freq=50000/}:S'
>
> and then since cycles is specified as a sampling event, it will use
> that.
Okay possible, but it makes things more complicated
for the user to understand and requires special documentation.
Hopefully it's worth it the internal simplification.
-andi
Powered by blists - more mailing lists