1. 21 5月, 2014 13 次提交
  2. 02 5月, 2014 1 次提交
  3. 28 4月, 2014 1 次提交
    • A
      perf tools: Allocate thread map_groups's dynamically · 93d5731d
      Arnaldo Carvalho de Melo 提交于
      Moving towards sharing map groups within a process threads.
      
      Because of this we need the map groups to be dynamically allocated. No
      other functional change is intended in here.
      
      Based on a patch by Jiri Olsa, but this time _just_ making the
      conversion from statically allocating thread->mg to turning it into a
      pointer and instead of initializing it at thread's constructor,
      introduce a constructor/destructor for the map_groups class and
      call at thread creation time.
      
      Later we will introduce the get/put methods when we move to sharing
      those map_groups, when the get/put refcounting semantics will be needed.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@kernel.org>
      Acked-by: NNamhyung Kim <namhyung@kernel.org>
      Cc: Adrian Hunter <adrian.hunter@intel.com>
      Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>
      Cc: David Ahern <dsahern@gmail.com>
      Cc: Don Zickus <dzickus@redhat.com>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Ingo Molnar <mingo@kernel.org>
      Cc: Mike Galbraith <efault@gmx.de>
      Cc: Namhyung Kim <namhyung@kernel.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Stephane Eranian <eranian@google.com>
      Link: http://lkml.kernel.org/r/1397490723-1992-3-git-send-email-jolsa@redhat.comSigned-off-by: NJiri Olsa <jolsa@kernel.org>
      93d5731d
  4. 24 4月, 2014 4 次提交
  5. 16 4月, 2014 2 次提交
  6. 15 3月, 2014 5 次提交
  7. 13 1月, 2014 1 次提交
  8. 28 12月, 2013 2 次提交
  9. 27 12月, 2013 1 次提交
  10. 26 12月, 2013 3 次提交
  11. 20 12月, 2013 1 次提交
  12. 15 11月, 2013 4 次提交
  13. 12 11月, 2013 1 次提交
    • P
      perf ui tui progress: Don't force a refresh during progress update · d53e57d0
      Patrick Palka 提交于
      Each call to tui_progress__update() would forcibly refresh the entire
      screen.  This is somewhat inefficient and causes noticable flickering
      during the startup of perf-report, especially on large/slow terminals.
      
      It looks like the force-refresh in tui_progress__update() serves no
      purpose other than to clear the screen so that the progress bar of a
      previous operation does not subsume that of a subsequent operation.  But
      we can do just that in a much more efficient manner by clearing only the
      region that a previous progress bar may have occupied before repainting
      the new progress bar.  Then the force-refresh could be removed with no
      change in visuals.
      
      This patch disables the slow force-refresh in tui_progress__update() and
      instead calls SLsmg_fill_region() on the entire area that the progress
      bar may occupy before repainting it.  This change makes the startup of
      perf-report much faster and appear much "smoother".
      
      It turns out that this was a big bottleneck in the startup speed of
      perf-report -- with this patch, perf-report starts up ~2x faster (1.1s
      vs 0.55s) on my machines.  (These numbers were measured by running "time
      perf report" on an 8MB perf.data and pressing 'q' immediately.)
      Signed-off-by: NPatrick Palka <patrick@parcs.ath.cx>
      Acked-by: NIngo Molnar <mingo@kernel.org>
      Cc: Ingo Molnar <mingo@kernel.org>
      Cc: Namhyung Kim <namhyung@kernel.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Link: http://lkml.kernel.org/r/1382747149-9716-1-git-send-email-patrick@parcs.ath.cxSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      d53e57d0
  14. 06 11月, 2013 1 次提交