public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Waiman Long <Waiman.Long@hp.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Jiri Olsa <jolsa@redhat.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	David Ahern <dsahern@gmail.com>,
	Stephane Eranian <eranian@google.com>,
	linux-kernel@vger.kernel.org,
	Aswin Chandramouleeswaran <aswin@hp.com>,
	Scott J Norton <scott.norton@hp.com>,
	Davidlohr Bueso <davidlohr@hp.com>
Subject: Re: [PATCH v3 0/3] perf: add option to limit callchain stack scan to increase speed
Date: Tue, 22 Oct 2013 18:07:05 +0000	[thread overview]
Message-ID: <871u3dkwmu.fsf@danjae.aot.lge.com> (raw)
In-Reply-To: <1382367819-19643-1-git-send-email-Waiman.Long@hp.com> (Waiman Long's message of "Mon, 21 Oct 2013 11:03:36 -0400")

Hi Waiman,

On Mon, 21 Oct 2013 11:03:36 -0400, Waiman Long wrote:
> v2->v3:
>  - Fix the commit log in the second patch which causes "git am" to fail.
>  - Remove the 1st patch in v2 as the problem will be fixed by another
>    patch from Arnaldo.
>
> v1->v2:
>  - Include a compilation fix patch and a code streamlining patch
>    into the patch set.
>  - Use the __stringify() macro in stringify.h instead of adding a
>    duplicate macro.
>  - Add the --max-stack option to perf-top as well.
>
> This perf patch set contains the following changes:
>
> Patch 1 - Streamline the append_chain() function to make it run a bit
>           faster.
> Patch 2 - Add a --max-stack option to perf-report to speed up its
>           processing at the expense of less backtrace information
>           available.
> Patch 3 - Add a similar --max-stack option to perf-top.

At first, thank you for tackling this.  It was really a problem using
callchain on non trivial perf session.  But there's another effort to
address this problem in other direction.  You might want to see below
link [1].  Patch 1/8 does the thing and it seems Arnaldo already merged
it into his tree.

Arnaldo, is there any issue prevents others from being merged?

[1] https://lkml.org/lkml/2013/10/11/16

Thanks,
Namhyung

  parent reply	other threads:[~2013-10-22  9:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 15:03 [PATCH v3 0/3] perf: add option to limit callchain stack scan to increase speed Waiman Long
2013-10-21 15:03 ` [PATCH v3 1/3] perf: streamline append_chain() function Waiman Long
2013-10-21 15:03 ` [PATCH v3 2/3] perf-report: add --max-stack option to limit callchain stack scan Waiman Long
2013-10-21 15:03 ` [PATCH v3 3/3] perf-top: " Waiman Long
2013-10-22 18:07 ` Namhyung Kim [this message]
2013-10-22 19:12   ` [PATCH v3 0/3] perf: add option to limit callchain stack scan to increase speed Waiman Long

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=871u3dkwmu.fsf@danjae.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=Waiman.Long@hp.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=adrian.hunter@intel.com \
    --cc=aswin@hp.com \
    --cc=davidlohr@hp.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=scott.norton@hp.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