mirror of https://lore.kernel.org/lkml/
 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,
	xiaoguangrong@linux.vnet.ibm.com, yangds.fnst@cn.fujitsu.com,
	adrian.hunter@intel.com, namhyung@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] perf trace pagefaults
Date: Fri, 20 Jun 2014 10:21:05 -0300	[thread overview]
Message-ID: <20140620132105.GE31524@kernel.org> (raw)
In-Reply-To: <1403261389-13423-1-git-send-email-stfomichev@yandex-team.ru>

Em Fri, Jun 20, 2014 at 02:49:42PM +0400, Stanislav Fomichev escreveu:
> This patch series adds support for pagefaults tracing to 'perf trace' command.
> It seems this feature was planned by Namhyung Kim (http://events.linuxfoundation.org/images/stories/pdf/klf2012_n_kim.pdf page 17/28)
> but I couldn't find any prior patches/discussion and started from scratch.

Just to clarify here, those slides came from slides I made and in turn
the whole idea about pagefaults tracing I got from the trace prototype
that Thomas Gleixner implemented in his 'trace'  utility, described
here:

  Announcing a new utility: 'trace'
  http://lwn.net/Articles/415728/

The comments section has lots of interesting ideas, some you may find
interesting to implement :-)

There is a branch in my tree with the branch tglx did his work on:

https://git.kernel.org/cgit/linux/kernel/git/acme/linux.git/log/?h=tmp.perf/trace2

There you can take a look and compare what you're doing to what he did.

Now I'll go thru your current patches and will cherry pick whatever I
think its OK already, and will try and provide comments for whatever I
think needs more work.

- Arnaldo
 
> First three patches add the feature and options to enable faults and disable
> syscalls.
> Two last patches add events caching (like it's done in the perf kvm), so that
> we don't get fault events prior to mmap/comm events (makes sense only
> for live mode).
> 
> This is just a proof-of-concept, and I'd like to get some comments about
> where and what I got wrong and what additional useful information I can
> expose in the trace.
> 
> v2:
>   - added more info to the changelogs
>   - reworked options (-f -> -F, --pgfaults -> --pf=[all|min|maj])
>   - separated tracepoint_handler changes into additional patch
>   - separated record/replay into additional patch
>   - other fixes pointed out by Arnaldo Carvalho de Melo
> 
> Stanislav Fomichev (7):
>   perf trace: add perf_event parameter to tracepoint_handler
>   perf trace: add support for pagefault tracing
>   perf trace: add pagefaults record and replay support
>   perf trace: add pagefault statistics
>   perf trace: add possibility to switch off syscall events
>   perf kvm: move perf_kvm__mmap_read into session utils
>   perf trace: add events cache
> 
>  tools/perf/Documentation/perf-trace.txt |  19 ++
>  tools/perf/builtin-kvm.c                |  88 +-------
>  tools/perf/builtin-trace.c              | 350 ++++++++++++++++++++++----------
>  tools/perf/util/session.c               |  85 ++++++++
>  tools/perf/util/session.h               |   5 +
>  5 files changed, 357 insertions(+), 190 deletions(-)
> 
> -- 
> 1.8.3.2

  parent reply	other threads:[~2014-06-20 13:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 10:49 Stanislav Fomichev
2014-06-20 10:49 ` [PATCH 1/7] perf trace: add perf_event parameter to tracepoint_handler Stanislav Fomichev
2014-06-20 10:49 ` [PATCH 2/7] perf trace: add support for pagefault tracing Stanislav Fomichev
2014-06-20 14:59   ` Arnaldo Carvalho de Melo
2014-06-20 15:49     ` Stanislav Fomichev
2014-06-20 16:11       ` Arnaldo Carvalho de Melo
2014-06-24 12:46         ` Stanislav Fomichev
2014-06-24 15:21           ` Arnaldo Carvalho de Melo
2014-06-20 10:49 ` [PATCH 3/7] perf trace: add pagefaults record and replay support Stanislav Fomichev
2014-06-20 10:49 ` [PATCH 4/7] perf trace: add pagefault statistics Stanislav Fomichev
2014-06-20 10:49 ` [PATCH 5/7] perf trace: add possibility to switch off syscall events Stanislav Fomichev
2014-06-20 10:49 ` [PATCH 6/7] perf kvm: move perf_kvm__mmap_read into session utils Stanislav Fomichev
2014-06-20 14:44   ` Arnaldo Carvalho de Melo
2014-06-20 15:07     ` Stanislav Fomichev
2014-06-20 15:25       ` Arnaldo Carvalho de Melo
2014-06-23 14:06     ` David Ahern
2014-06-23 14:14       ` Stanislav Fomichev
2014-06-20 10:49 ` [PATCH 7/7] perf trace: add events cache Stanislav Fomichev
2014-06-20 13:21 ` Arnaldo Carvalho de Melo [this message]
2014-06-20 15:03   ` [PATCH v2 0/7] perf trace pagefaults Stanislav Fomichev
2014-06-20 15:24     ` Arnaldo Carvalho de Melo
2014-06-20 16:18       ` Stanislav Fomichev
2014-06-20 18:30         ` Arnaldo Carvalho de Melo
2014-06-23 11:41           ` Stanislav Fomichev
2014-06-24 14:15             ` Arnaldo Carvalho de Melo
2014-06-23 14:00       ` David Ahern
2014-06-24  7:17   ` Namhyung Kim

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=20140620132105.GE31524@kernel.org \
    --to=acme@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=adrian.hunter@intel.com \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=stfomichev@yandex-team.ru \
    --cc=xiaoguangrong@linux.vnet.ibm.com \
    --cc=yangds.fnst@cn.fujitsu.com \
    /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

Powered by JetHome