linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stanislav Fomichev <stfomichev@yandex-team.ru>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
	dsahern@gmail.com, jolsa@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] perf trace: add pagefault statistics
Date: Thu, 26 Jun 2014 16:41:15 -0300	[thread overview]
Message-ID: <20140626194115.GE18773@kernel.org> (raw)
In-Reply-To: <1403799268-1367-5-git-send-email-stfomichev@yandex-team.ru>

Em Thu, Jun 26, 2014 at 08:14:27PM +0400, Stanislav Fomichev escreveu:
> 'perf trace' can show summary of events using -S option. This commit
> also reports number of major/minor pagefault events in this summary.
> 
> Signed-off-by: Stanislav Fomichev <stfomichev@yandex-team.ru>

Where is it?

[root@zoo /]# perf trace -S -F all -- usleep 1 | tail -30
Failed to open /etc/ld.so.cache, continuing without symbols
     1.241 ( 0.001 ms): brk(                                                                  ) = 0x24c9000
     1.245 ( 0.003 ms): brk(brk: 0x24ea000                                                    ) = 0x24ea000
     1.248 ( 0.001 ms): brk(                                                                  ) = 0x24ea000
     1.253 ( 0.000 ms): minfault [_int_malloc+0x116a] => [heap]@0x24c9008 (d.)
     1.268 ( 0.000 ms): minfault [__GI_____strtoull_l_internal+0x47] => /usr/lib64/libc-2.18.so@0x164ae3 (x.)
     1.273 ( 0.000 ms): minfault [__GI___libc_nanosleep+0x0] => /usr/lib64/libc-2.18.so@0xbc960 (x.)
     1.336 ( 0.062 ms): nanosleep(rqtp: 0x7fff30ccf640                                        ) = 0
     1.344 ( 0.000 ms): exit_group(                                                           

 Summary of events:

 usleep (19155), 151 events, 84.4%, 0:68 faults, 0.000 msec

   syscall            calls      min       avg       max      stddev
                               (msec)    (msec)    (msec)        (%)
   --------------- -------- --------- --------- ---------     ------
   read                   3     0.000     0.002     0.003     50.38%
   open                   3     0.006     0.007     0.008      8.51%
   close                  3     0.001     0.001     0.002      6.05%
   fstat                  3     0.001     0.002     0.002      7.70%
   mmap                   9     0.003     0.005     0.006      9.56%
   mprotect               6     0.004     0.007     0.010     14.12%
   munmap                 1     0.013     0.013     0.013      0.00%
   brk                    4     0.001     0.002     0.003     28.94%
   access                 1     0.007     0.007     0.007      0.00%
   nanosleep              1     0.062     0.062     0.062      0.00%
   execve                 7     0.000     0.086     0.574     94.41%
   arch_prctl             1     0.002     0.002     0.002      0.00%


[root@zoo /]# 

-----------------------------------------

There were minor page faults, were in the summary are they?

I haven't even looked at the code, first I wanted to check if just doing what
is expected would work, i.e. enable all the page fault types, run a workload,
ask for -S and check if there were any stats for major and minor page faults.

I can update the changelog comment with an example if you tell me what I am
doing wrong.

Applied and tested the previous patches.

- Arnaldo

  reply	other threads:[~2014-06-26 19:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 16:14 [PATCH v3 0/5] perf trace pagefaults Stanislav Fomichev
2014-06-26 16:14 ` [PATCH 1/5] perf trace: add perf_event parameter to tracepoint_handler Stanislav Fomichev
2014-07-05 10:40   ` [tip:perf/core] perf trace: Add " tip-bot for Stanislav Fomichev
2014-06-26 16:14 ` [PATCH 2/5] perf trace: add support for pagefault tracing Stanislav Fomichev
2014-07-05 10:41   ` [tip:perf/core] perf trace: Add " tip-bot for Stanislav Fomichev
2014-06-26 16:14 ` [PATCH 3/5] perf trace: add pagefaults record and replay support Stanislav Fomichev
2014-07-05 10:41   ` [tip:perf/core] perf trace: Add " tip-bot for Stanislav Fomichev
2014-06-26 16:14 ` [PATCH 4/5] perf trace: add pagefault statistics Stanislav Fomichev
2014-06-26 19:41   ` Arnaldo Carvalho de Melo [this message]
2014-06-27  8:43     ` Stanislav Fomichev
2014-06-27 13:53       ` Arnaldo Carvalho de Melo
2014-06-27 15:44         ` Stanislav Fomichev
2014-06-27 21:16           ` Arnaldo Carvalho de Melo
2014-06-26 16:14 ` [PATCH 5/5] perf trace: add possibility to switch off syscall events Stanislav Fomichev
2014-07-05 10:41   ` [tip:perf/core] perf trace: Add " tip-bot for Stanislav Fomichev

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=20140626194115.GE18773@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=stfomichev@yandex-team.ru \
    /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).