From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/4] Annotation improvements for perf/core
Date: Wed, 30 May 2012 09:03:41 +0200 [thread overview]
Message-ID: <20120530070341.GB2587@gmail.com> (raw)
In-Reply-To: <1338343002-5271-1-git-send-email-acme@infradead.org>
* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> Hi Ingo,
>
> Please consider pulling, contains what is in my perf/urgent branch.
>
> - Arnaldo
>
> The following changes since commit a44b45f236dd1c1a8caccf9a078adf2941a20267:
>
> perf annotate browser: The idx_asm field should be used in asm only view (2012-05-29 20:52:38 -0300)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux tags/perf-core-for-mingo
>
> for you to fetch changes up to 05e8b0804ec423a440882e7adecb36e7ac43e56f:
>
> perf ui browser: Stop using 'self' (2012-05-29 22:42:18 -0300)
>
> ----------------------------------------------------------------
> Annotation improvements for perf/core
>
> . Make the annotatation toggles (hide_src_code, jump_arrows, use_offset, etc)
> global so that navigation doesn't resets them on new annotations.
>
> . Introduce an '[annotate]' config file section to allow permanent changes
> to the annotate browser defaults.
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> ----------------------------------------------------------------
> Arnaldo Carvalho de Melo (4):
> perf annotate browser: Make feature toggles global
> perf config: Allow '_' in config file variable names
> perf annotate browser: Read perf config file for settings
> perf ui browser: Stop using 'self'
>
> tools/perf/Documentation/perfconfig.example | 8 +
> tools/perf/ui/browser.c | 182 ++++++++-------
> tools/perf/ui/browser.h | 1 +
> tools/perf/ui/browsers/annotate.c | 258 +++++++++++++-------
> tools/perf/ui/browsers/hists.c | 338 +++++++++++++--------------
> tools/perf/util/config.c | 2 +-
> 6 files changed, 440 insertions(+), 349 deletions(-)
Pulled, thanks!
Ingo
prev parent reply other threads:[~2012-05-30 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 1:56 [GIT PULL 0/4] Annotation improvements for perf/core Arnaldo Carvalho de Melo
2012-05-30 1:56 ` [PATCH 1/4] perf annotate browser: Make feature toggles global Arnaldo Carvalho de Melo
2012-05-30 1:56 ` [PATCH 2/4] perf config: Allow '_' in config file variable names Arnaldo Carvalho de Melo
2012-05-30 1:56 ` [PATCH 3/4] perf annotate browser: Read perf config file for settings Arnaldo Carvalho de Melo
2012-05-30 1:56 ` [PATCH 4/4] perf ui browser: Stop using 'self' Arnaldo Carvalho de Melo
2012-05-30 7:03 ` Ingo Molnar [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=20120530070341.GB2587@gmail.com \
--to=mingo@kernel.org \
--cc=acme@infradead.org \
--cc=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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