[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141105162723.GW3337@twins.programming.kicks-ass.net>
Date: Wed, 5 Nov 2014 17:27:23 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: "Liang, Kan" <kan.liang@...el.com>
Cc: "eranian@...gle.com" <eranian@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"paulus@...ba.org" <paulus@...ba.org>,
"acme@...nel.org" <acme@...nel.org>,
"jolsa@...hat.com" <jolsa@...hat.com>,
"ak@...ux.intel.com" <ak@...ux.intel.com>
Subject: Re: [PATCH V7 00/17] perf, x86: Haswell LBR call stack support
On Wed, Nov 05, 2014 at 04:22:09PM +0000, Liang, Kan wrote:
>
> >>
> >
> > So if I take all except 11,13,16,17 but instead do something like the below,
> > everything will work just fine, right?
> >
> > Or am I missing something?
> >
>
> Yes, it should work. Then LBR callstack will rely on user to enable it.
> But user never get the LBR callstack data if it's available.
> I'm not sure why you do that?
Uhm what? If you request PERF_SAMPLE_BRANCH_CALL_STACK the user will get
the data through the regular PERF_SAMPLE_BRANCH_STACK output of
PERF_RECORD_SAMPLE, right?
--
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