All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>, Jiri Olsa <jolsa@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] perf stat: Basic support for TopDown in perf stat
Date: Mon, 6 Jun 2016 11:00:03 -0300	[thread overview]
Message-ID: <20160606140003.GD8679@kernel.org> (raw)
In-Reply-To: <20160530161942.GD11853@kernel.org>

Em Mon, May 30, 2016 at 01:19:42PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, May 30, 2016 at 09:04:02AM -0700, Andi Kleen escreveu:
> > > Which is a Broadwell-U, dual-core, 14 nm.
> > > 
> > > [root@jouet linux]# echo 0 > /proc/sys/kernel/nmi_watchdog
> > > [root@jouet linux]# perf stat --topdown -a usleep 1
> > > System does not support topdown
> > > [root@jouet linux]# cat /proc/sys/kernel/nmi_watchdog
> > > 0
> > > [root@jouet linux]#
> > > 
> > > Please advise.
> > 
> > You don't have the kernel patches?
> > 
> > They're in PeterZ's tree, but not yet in tip
> > https://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git/log/?h=perf/core
> 
> oops, will try applying those patches, thanks for claryfing.

The kernel patches are in tip/perf/core now, so I applied the patches
and they seem to work, but they broke one 'perf test' entry:

# perf test 5
 5: parse events tests                                       : FAILED!

# perf test -v 5
<SNIP>
running test 50 '4:0x6530160/name=numpmu/'
running test 51 'L1-dcache-misses/name=cachepmu/'
running test 0 'cpu/config=10,config1,config2=3,period=1000/u'
running test 1 'cpu/config=1,name=krava/u,cpu/config=2/u'
running test 2 'cpu/config=1,call-graph=fp,time,period=100000/,cpu/config=2,call-graph=no,time=0,period=2000/'
Invalid sysfs entry event=topdown-recovery-bubbles.scale
failed to parse event 'cpu/event=topdown-recovery-bubbles.scale/u', err 1
test child finished with 1
---- end ----
parse events tests: FAILED!
#

Please check that,

- Arnaldo

  reply	other threads:[~2016-06-06 14:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 19:52 [PATCH 1/4] perf stat: Basic support for TopDown in perf stat Andi Kleen
2016-05-24 19:52 ` [PATCH 2/4] perf stat: Add computation of TopDown formulas Andi Kleen
2016-06-01 14:50   ` Nilay Vaish
2016-06-01 14:56     ` Andi Kleen
2016-06-02 11:56       ` Nilay Vaish
2016-06-02 14:26         ` Andi Kleen
2016-06-08  8:39   ` [tip:perf/core] " tip-bot for Andi Kleen
2016-05-24 19:52 ` [PATCH 3/4] perf stat: Print topology/time headers with --metric-only Andi Kleen
2016-06-08  8:39   ` [tip:perf/core] " tip-bot for Andi Kleen
2016-05-24 19:52 ` [PATCH 4/4] perf stat: Add missing aggregation headers for --metric-only CSV Andi Kleen
2016-06-08  8:40   ` [tip:perf/core] " tip-bot for Andi Kleen
2016-05-30 16:01 ` [PATCH 1/4] perf stat: Basic support for TopDown in perf stat Arnaldo Carvalho de Melo
2016-05-30 16:04   ` Andi Kleen
2016-05-30 16:19     ` Arnaldo Carvalho de Melo
2016-06-06 14:00       ` Arnaldo Carvalho de Melo [this message]
2016-06-06 14:11         ` Arnaldo Carvalho de Melo
2016-06-06 14:36           ` Andi Kleen
2016-06-01 14:24 ` Nilay Vaish
2016-06-01 14:31   ` Andi Kleen
2016-06-01 15:24   ` Andi Kleen
2016-06-02 11:52     ` Nilay Vaish
2016-06-08  8:38 ` [tip:perf/core] " tip-bot for Andi Kleen

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=20160606140003.GD8679@kernel.org \
    --to=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.