From: Jiri Olsa <jolsa@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kan.liang@intel.com, acme@kernel.org, tglx@linutronix.de,
mingo@redhat.com, linux-kernel@vger.kernel.org,
eranian@google.com, jolsa@kernel.org, elliott@hpe.com,
ak@linux.intel.com
Subject: Re: [PATCH V2 0/2] measure SMI cost (user)
Date: Mon, 29 May 2017 15:16:42 +0200 [thread overview]
Message-ID: <20170529131642.GA3570@krava> (raw)
In-Reply-To: <20170529125239.sxd7dp4gyjjtws5z@hirez.programming.kicks-ass.net>
On Mon, May 29, 2017 at 02:52:39PM +0200, Peter Zijlstra wrote:
> On Mon, May 29, 2017 at 02:46:37PM +0200, Jiri Olsa wrote:
>
> > for some reason I can't get single SMI count generated,
> > is there a setup/bench that would provoke that?
>
> Not having SMIs is a good thing ;-)
>
> Not sure we can tickle them in a reliable way.
yea I saw some counts last time, now just zero
so I was wondering if it's working
jirka
next prev parent reply other threads:[~2017-05-29 13:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 19:05 [PATCH V2 0/2] measure SMI cost (user) kan.liang
2017-05-26 19:05 ` [PATCH V2 1/2] tools lib api fs: Add sysfs__write_int function kan.liang
2017-06-21 18:17 ` [tip:perf/core] " tip-bot for Kan Liang
2017-05-26 19:05 ` [PATCH V2 2/2] perf stat: Add support to measure SMI cost kan.liang
2017-06-21 18:18 ` [tip:perf/core] " tip-bot for Kan Liang
2017-05-29 12:46 ` [PATCH V2 0/2] measure SMI cost (user) Jiri Olsa
2017-05-29 12:52 ` Peter Zijlstra
2017-05-29 13:16 ` Jiri Olsa [this message]
2017-05-29 17:06 ` Liang, Kan
2017-06-02 15:45 ` Liang, Kan
2017-06-02 18:27 ` Arnaldo Carvalho de Melo
2017-06-14 17:50 ` Liang, Kan
2017-06-20 13:43 ` Liang, Kan
2017-06-20 20:29 ` 'Arnaldo Carvalho de Melo'
2017-06-20 21:43 ` Jiri Olsa
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=20170529131642.GA3570@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=elliott@hpe.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.