From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
LKML <linux-kernel@vger.kernel.org>,
Chris Zankel <chris@zankel.net>, Marc Gauthier <marc@cadence.com>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v2 07/13] xtensa: implement counting and sampling perf events
Date: Fri, 7 Aug 2015 10:12:05 -0300 [thread overview]
Message-ID: <20150807131205.GB3325@kernel.org> (raw)
In-Reply-To: <CAMo8Bf+qsVRc6G3WvrKh0JiJTX64Ae6SxyBLfSFZG7sJLLVOMA@mail.gmail.com>
Em Fri, Aug 07, 2015 at 03:03:02PM +0300, Max Filippov escreveu:
> On Fri, Aug 7, 2015 at 12:13 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> > 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
> >> 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.
> Right, had the same idea.
Ok, when you do that, i.e. get the kernel bits in, the tooling part will
be there, as it was already pulled by Ingo, i.e. its in tip.git and thus
should hit 4.3.
- ARnaldo
next prev parent reply other threads:[~2015-08-07 13:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 8:30 [PATCH v2 00/13] Support hardware perf counters on xtensa Max Filippov
2015-07-18 8:30 ` [PATCH v2 01/13] xtensa: clean up Kconfig dependencies for custom cores Max Filippov
2015-07-18 8:30 ` [PATCH v2 02/13] xtensa: keep exception/interrupt stack continuous Max Filippov
2015-07-18 8:30 ` [PATCH v2 03/13] xtensa: move oprofile stack tracing to stacktrace.c Max Filippov
2015-07-18 8:30 ` [PATCH v2 04/13] xtensa: select PERF_USE_VMALLOC for cache-aliasing configurations Max Filippov
2015-07-18 8:30 ` [PATCH v2 05/13] xtensa: add profiling IRQ type to xtensa_irq_map Max Filippov
2015-07-18 8:30 ` [PATCH v2 06/13] xtensa: count software page fault perf events Max Filippov
2015-07-18 8:30 ` [PATCH v2 07/13] xtensa: implement counting and sampling " Max Filippov
2015-08-06 19:46 ` Arnaldo Carvalho de Melo
2015-08-07 9:13 ` Peter Zijlstra
2015-08-07 12:03 ` Max Filippov
2015-08-07 13:12 ` Arnaldo Carvalho de Melo [this message]
2015-07-18 8:30 ` [PATCH v2 08/13] perf tools: xtensa: add DWARF register names Max Filippov
2015-08-07 7:22 ` [tip:perf/core] perf tools xtensa: Add " tip-bot for Max Filippov
2015-07-18 8:30 ` [PATCH v2 09/13] xtensa: reorganize irq flags tracing Max Filippov
2015-07-18 8:30 ` [PATCH v2 10/13] xtensa: fix kernel register spilling Max Filippov
2015-07-18 8:30 ` [PATCH v2 11/13] xtensa: don't touch EXC_TABLE_FIXUP in _switch_to Max Filippov
2015-07-18 8:30 ` [PATCH v2 12/13] xtensa: implement fake NMI Max Filippov
2015-07-27 14:36 ` Max Filippov
2015-07-27 15:14 ` Peter Zijlstra
2015-07-18 8:30 ` [PATCH v2 13/13] xtensa: drop unused irq_err_count Max Filippov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150807131205.GB3325@kernel.org \
--to=acme@kernel.org \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=marc@cadence.com \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox