From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752121AbbHGJOJ (ORCPT ); Fri, 7 Aug 2015 05:14:09 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:45505 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750809AbbHGJOA (ORCPT ); Fri, 7 Aug 2015 05:14:00 -0400 Date: Fri, 7 Aug 2015 11:13:52 +0200 From: Peter Zijlstra To: Arnaldo Carvalho de Melo Cc: Max Filippov , linux-xtensa@linux-xtensa.org, linux-kernel@vger.kernel.org, Chris Zankel , Marc Gauthier , Paul Mackerras , Ingo Molnar Subject: Re: [PATCH v2 07/13] xtensa: implement counting and sampling perf events Message-ID: <20150807091352.GD16853@twins.programming.kicks-ass.net> References: <1437208216-15729-1-git-send-email-jcmvbkbc@gmail.com> <1437208216-15729-8-git-send-email-jcmvbkbc@gmail.com> <20150806194632.GC10826@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150806194632.GC10826@kernel.org> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 06, 2015 at 04:46:32PM -0300, Arnaldo Carvalho de Melo wrote: > Em Sat, Jul 18, 2015 at 11:30:10AM +0300, Max Filippov escreveu: > > Xtensa Performance Monitor Module has up to 8 32 bit wide performance > > counters. Each counter may be enabled independently and can count any > > single type of hardware performance events. Event counting may be enabled > > and disabled globally (per PMM). > > Each counter has status register with bits indicating if the counter has > > been overflown and may be programmed to raise profiling IRQ on overflow. > > This IRQ is used to rewind counters and allow for counting more than 2^32 > > samples for counting events and to report samples for sampling events. > > > > For more details see Tensilica Debug User's Guide, chapter 8 > > "Performance monitor module". > > Has this gone via PeterZ? I added the tools/ bits in my perf/core > branch, will go in next pull req, I was thinking it would go through the xtensa tree. Looks fine at a quick glance and they can actually test it.