[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABPqkBTTZaCVTtwJZbjXGwAihKAW_PMFK0+TZUTvbOn4pnfzvA@mail.gmail.com>
Date: Fri, 6 Jul 2012 03:42:54 +0200
From: Stephane Eranian <eranian@...gle.com>
To: Ulrich Drepper <drepper@...il.com>
Cc: Jiri Olsa <jolsa@...hat.com>, Namhyung Kim <namhyung@...il.com>,
acme@...hat.com, a.p.zijlstra@...llo.nl, mingo@...e.hu,
paulus@...ba.org, cjashfor@...ux.vnet.ibm.com, fweisbec@...il.com,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
andi@...stfloor.org
Subject: Re: [PATCHv3 0/3] perf tool: Add new event group management
On Fri, Jul 6, 2012 at 3:32 AM, Ulrich Drepper <drepper@...il.com> wrote:
> On Thu, Jul 5, 2012 at 12:15 PM, Stephane Eranian <eranian@...gle.com> wrote:
>> I don't understand why you actually need the :2 suffix. There can
>> only be one leader. So assume it is the first one. Users have to
>> know the first one is the leader which seems like a natural thing
>> to do for me. It would make you syntax less ugly than it already
>> is.
>
> In a blue sky world I would have done this. In fact, this is what I
> tried before reading the sources to find out there is no group support
> so far. But given that multiple -e options already have a meaning I
> would be hesitant to change this.
That's why I said you activate grouping via -e only when you have
the --group-events or --group-reads option in front. That would
not change the meaning of the multiple -e when none of those
group options are specified.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists