mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
	Paul Mackerras <paulus@samba.org>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 0/3] perf: add a dummy software event to keep tracking
Date: Tue, 13 Aug 2013 11:28:45 +0900	[thread overview]
Message-ID: <87mwomwcgy.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1375882231-18339-1-git-send-email-adrian.hunter@intel.com> (Adrian Hunter's message of "Wed, 7 Aug 2013 16:30:28 +0300")

Hi Adrian,

On Wed,  7 Aug 2013 16:30:28 +0300, Adrian Hunter wrote:
> Hi
>
> This is an alternative to the 'keep tracking' flag patch
> which is here:
>
> 	http://marc.info/?l=linux-kernel&m=137242545521246&w=2
>
> perf tools is updated and a test added to demonstrate the
> new event.

It looks like a perfect fit for tracking fork/mmap events on
perf-ftrace. :)

Thanks,
Namhyung

      parent reply	other threads:[~2013-08-13  2:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 13:30 Adrian Hunter
2013-08-07 13:30 ` [PATCH 1/3] " Adrian Hunter
2013-08-26 13:15   ` Adrian Hunter
2013-08-26 13:53     ` Arnaldo Carvalho de Melo
2013-08-26 16:16       ` Peter Zijlstra
2013-08-07 13:30 ` [PATCH 2/3] perf tools: add support for PERF_COUNT_SW_DUMMY Adrian Hunter
2013-08-07 13:30 ` [PATCH 3/3] perf tools: add 'keep tracking' test Adrian Hunter
2013-08-13  2:33   ` Namhyung Kim
2013-08-26 13:13     ` Adrian Hunter
2013-08-13  2:28 ` Namhyung Kim [this message]

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=87mwomwcgy.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=adrian.hunter@intel.com \
    --cc=dsahern@gmail.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.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
Powered by JetHome