From: Andi Kleen <andi@firstfloor.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, acme@redhat.com, peterz@infradead.org,
        mingo@elte.hu, jolsa@redhat.com, namhyung@kernel.org,
        kan.liang@intel.com, dsahern@gmail.com, adrian.hunter@intel.com
Subject: Re: [PATCH v2 4/4] perf script: enable printing of branch stack
References: <1441039273-16260-1-git-send-email-eranian@google.com>
	<1441039273-16260-5-git-send-email-eranian@google.com>
	<20150831170535.GY4524@tassilo.jf.intel.com>
Date: Mon, 31 Aug 2015 10:08:01 -0700
In-Reply-To: <20150831170535.GY4524@tassilo.jf.intel.com> (Andi Kleen's
	message of "Mon, 31 Aug 2015 10:05:35 -0700")
Message-ID: <874mjfxu6m.fsf@tassilo.jf.intel.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 875
Lines: 28

Andi Kleen <ak@linux.intel.com> writes:

>>  $ perf script -F ip,brstack
>>   5d3000 0x401aa0/0x5d2000/M/-/-/-/0 ...
>> 
>>  $ perf script -F ip,brstacksym
>>   4011e0 noploop+0x0/noploop+0x0/P/-/-/0
>
> That's a weird format that's hard to parse with standard tools like
> awk, and also for humans. How about separating with spaces?

Also can you include the number of the LBR in the branch record?
That can be useful sometimes.

BTW I haven't checked, but it would be also good to make sure
the print order is the same as program order (perf stores
the LBRs reversed)

-Andi


-- 
ak@linux.intel.com -- Speaking for myself only
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/