linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Adrian Hunter <adrian.hunter@intel.com>,
	Borislav Petkov <bp@suse.de>, David Ahern <dsahern@gmail.com>,
	Don Zickus <dzickus@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	He Kuang <hekuang@huawei.com>, Jiri Olsa <jolsa@redhat.com>,
	Li Zhang <zhlcindy@linux.vnet.ibm.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Naohiro Aota <naota@elisp.net>,
	Peter Zijlstra <peterz@infradead.org>,
	pi3orama@163.com, Stephane Eranian <eranian@google.com>,
	Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
	Wang Nan <wangnan0@huawei.com>, Zefan Li <lizefan@huawei.com>
Subject: Re: [RFC] hotkey for disabling/enabling events in 'perf top' TUI was Re: [GIT PULL 0/8] perf/core improvements and fixes
Date: Thu, 18 Jun 2015 22:58:13 +0200	[thread overview]
Message-ID: <20150618205813.GA476@gmail.com> (raw)
In-Reply-To: <20150618201829.GF3079@kernel.org>


* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:

> Em Thu, Jun 18, 2015 at 09:40:10AM +0200, Ingo Molnar escreveu:
> > * Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > > User visible:
> 
> > > - Allow disabling/enabling events dynamicly in 'perf top':
> > >   a 'perf top' session can instantly become a 'perf report'
> > >   one, i.e. going from dynamic analysis to a static one,
> > >   returning to a dynamic one is possible, to toogle the
> > >   modes, just press CTRL+z. (Arnaldo Carvalho de Melo)
>  
> > Nice!! :-)
>  
> > Btw., it would be nice if the status line carried information about whether 
> > collection is 'frozen' or running, at a glance. A hint might also suggest how to 
> > unfreeze the session - in case someone pressed Ctrl-Z to suspend the perf top 
> > session ...
> 
> Right, and I think we better find other hotkey and make Ctrl+Z work like
> with other tools, i.e. suspend:
> 
> [acme@zoo linux]$ mutt
> 
> [1]+  Stopped                 mutt
> [acme@zoo linux]$ vim
> 
> [2]+  Stopped                 vim
> [acme@zoo linux]$ 
> 
> The perf TUI should work like that as well...
> 
> Ideas?
> 
> We already have:
> 
> h/?/F1        Show this window
> UP/DOWN/PGUP
> PGDN/SPACE    Navigate
> q/ESC/CTRL+C  Exit browser
> 
> For multiple event sessions:
> 
> TAB/UNTAB     Switch events
> 
> For symbolic views (--sort has sym):
> 
> ->            Zoom into DSO/Threads & Annotate current symbol
> <-            Zoom out
> a             Annotate current symbol
> C             Collapse all callchains
> d             Zoom into current DSO
> D             Show some developer debug info
> E             Expand all callchains
> F             Toggle percentage of filtered entries
> H             Display column headers
> i             Show header information
> P             Print histograms to perf.hist.N
> r             Run available scripts
> s             Switch to another data file in PWD
> t             Zoom into current Thread
> V             Verbose (DSO names in callchains, etc)
> z             Toggle zeroing of samples 
> /             Filter symbol by name 

Is 'f' (for 'freeze') still available?

Thanks,

	Ingo

  reply	other threads:[~2015-06-18 20:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 21:22 [GIT PULL 0/8] perf/core improvements and fixes Arnaldo Carvalho de Melo
2015-06-17 21:22 ` [PATCH 1/8] perf tools: Ignore .config-detected in .gitignore Arnaldo Carvalho de Melo
2015-06-17 21:22 ` [PATCH 2/8] perf tools: Fix a problem when opening old perf.data with different byte order Arnaldo Carvalho de Melo
2015-06-17 21:22 ` [PATCH 3/8] perf tools: Move libtraceevent dynamic list to separated LDFLAGS variable Arnaldo Carvalho de Melo
2015-06-17 21:22 ` [PATCH 4/8] perf probe: Show usage even if the last event is skipped Arnaldo Carvalho de Melo
2015-06-17 21:22 ` [PATCH 5/8] perf probe: Speed up perf probe --list by caching debuginfo Arnaldo Carvalho de Melo
2015-06-17 21:22 ` [PATCH 6/8] perf trace: Fix race condition at the end of started workloads Arnaldo Carvalho de Melo
2015-06-17 21:22 ` [PATCH 7/8] perf evlist: Add toggle_enable() method Arnaldo Carvalho de Melo
2015-06-17 21:22 ` [PATCH 8/8] perf top: Allow disabling/enabling events dynamicly Arnaldo Carvalho de Melo
2015-06-18  7:40 ` [GIT PULL 0/8] perf/core improvements and fixes Ingo Molnar
2015-06-18 20:18   ` [RFC] hotkey for disabling/enabling events in 'perf top' TUI was " Arnaldo Carvalho de Melo
2015-06-18 20:58     ` Ingo Molnar [this message]
2015-06-18 21:39       ` Arnaldo Carvalho de Melo
2015-06-19  6:27         ` Ingo Molnar
2015-06-19 20:07           ` Arnaldo Carvalho de Melo
2015-06-19 23:05             ` Ingo Molnar
2015-06-22 14:52               ` Arnaldo Carvalho de Melo

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=20150618205813.GA476@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=bp@suse.de \
    --cc=dsahern@gmail.com \
    --cc=dzickus@redhat.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=hekuang@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=namhyung@kernel.org \
    --cc=naota@elisp.net \
    --cc=peterz@infradead.org \
    --cc=pi3orama@163.com \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=wangnan0@huawei.com \
    --cc=zhlcindy@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).