From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Milian Wolff <milian.wolff@kdab.com>,
linux-perf-users@vger.kernel.org, namhyung@kernel.org,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: measuring system wide CPU usage ignoring idle process
Date: Thu, 23 Nov 2017 15:59:41 -0300 [thread overview]
Message-ID: <20171123185941.GN8789@kernel.org> (raw)
In-Reply-To: <20171123151205.GA8342@krava>
Em Thu, Nov 23, 2017 at 04:12:05PM +0100, Jiri Olsa escreveu:
> On Thu, Nov 23, 2017 at 11:42:20AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Nov 23, 2017 at 03:21:00PM +0100, Jiri Olsa escreveu:
> > > On Thu, Nov 23, 2017 at 03:09:31PM +0100, Jiri Olsa wrote:
> > > > On Thu, Nov 23, 2017 at 02:40:36PM +0100, Milian Wolff wrote:
> > > > > > > Sorry for being unclear: I was talking about the task-clock and cpu-clock
> > > > > > > values which you omitted from your measurements below. My example also
> > > > > > > shows that the counts for cycles and instructions are fine. But the
> > > > > > > cpu-clock and task-clock are useless as they always sum up to essentially
> > > > > > > `$nproc*$runtime`. What I'm hoping for are fractional values for the "N
> > > > > > > CPUs utilized".
> > > > > > ugh my bad.. anyway by using -a you create cpu counters
> > > > > > which never unschedule, so those times will be same
> > > > > > as the 'sleep 1' run length
> > Humm, what role perf_event_attr.exclude_idle has here?
> it's used for omiting samples from idle process.. but looks like it's
> enforced for software clock events
looks like it is NOT enforced?
> AFAICS it's not used in counting mode
But it should? I think it should, as we see from Milian's use case.
PeterZ sent a patch, I guess we should continue from there :-)
- Arnaldo
next prev parent reply other threads:[~2017-11-23 18:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 14:00 measuring system wide CPU usage ignoring idle process Milian Wolff
2017-11-20 14:29 ` Jiri Olsa
2017-11-20 20:24 ` Milian Wolff
2017-11-20 23:44 ` Jiri Olsa
2017-11-23 13:40 ` Milian Wolff
2017-11-23 14:09 ` Jiri Olsa
2017-11-23 14:21 ` Jiri Olsa
2017-11-23 14:42 ` Arnaldo Carvalho de Melo
2017-11-23 15:12 ` Jiri Olsa
2017-11-23 18:59 ` Arnaldo Carvalho de Melo [this message]
2017-11-24 8:14 ` Jiri Olsa
2017-11-23 15:15 ` Peter Zijlstra
2018-04-17 13:41 ` Arnaldo Carvalho de Melo
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=20171123185941.GN8789@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).