linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] perf changes
Date: Tue, 25 May 2010 10:22:21 +1000	[thread overview]
Message-ID: <20100525002221.GA30395@drongo> (raw)
In-Reply-To: <20100524192531.GA15614@elte.hu>

On Mon, May 24, 2010 at 09:25:31PM +0200, Ingo Molnar wrote:

> Please pull the latest perf-core-for-linus git tree from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git perf-core-for-linus
> 
> Most of these changes are fixes and dead code removal, but 
> also a set of optimizations and a series of tracing 
> size-optimization bits that we kept pending because they 
> conflicted with the previous push - and some TUI 
> enhancements.

...

> Peter Zijlstra (16):
>       perf/ftrace: Optimize perf/tracepoint interaction for single events
>       perf: Optimize buffer placement by allocating buffers NUMA aware
>       perf: Disallow mmap() on per-task inherited events
>       perf: Optimize the perf_output() path by removing IRQ-disables
>       perf: Optimize the hotpath by converting the perf output buffer to local_t
>       perf: Optimize perf_output_*() by avoiding local_xchg()
>       perf, trace: Optimize tracepoints by removing IRQ-disable from perf/tracepoint interaction

This commit breaks all non-x86 architectures by adding a reference to
regs->flags in generic code.  I mentioned this on lkml (with cc to
Ingo and Peter), and Peter has a further patch that fixes the problem,
which isn't in this pull.

So Linus, please don't do this pull just yet, until we get this extra
patch merged.

Paul.

  reply	other threads:[~2010-05-25  0:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 19:25 [GIT PULL] perf changes Ingo Molnar
2010-05-25  0:22 ` Paul Mackerras [this message]
2010-05-25 13:52   ` [GIT PULL, v2] " Ingo Molnar
2010-05-27 22:34     ` Linus Torvalds
2010-05-27 23:08       ` Arnaldo Carvalho de Melo
2010-05-28  0:32       ` Steven Rostedt
2010-05-28  0:43         ` Arnaldo Carvalho de Melo
2010-05-28  7:00       ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2016-01-11 12:56 [GIT PULL] " Ingo Molnar
2016-01-11 23:07 ` Stephen Rothwell

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=20100525002221.GA30395@drongo \
    --to=paulus@samba.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).