public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Kumar Gala <kumar.gala@freescale.com>,
	linux-kernel@vger.kernel.org,
	"David S.Miller" <davem@davemloft.net>,
	linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>,
	jbaron@redhat.com
Subject: Re: [PATCH] powerpc: Add jump label support
Date: Tue, 09 Nov 2010 14:33:00 +1100	[thread overview]
Message-ID: <1289273580.21111.193.camel@concordia> (raw)
In-Reply-To: <1289225915.12418.2.camel@gandalf.stny.rr.com>

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]

On Mon, 2010-11-08 at 09:18 -0500, Steven Rostedt wrote:
> On Mon, 2010-11-08 at 15:12 +1100, Michael Ellerman wrote:
> > This patch adds support for the new "jump label" feature.
> 
> Darn it! I wanted to port this!!!
> 
> ;-)

Sorry! I've been locked in a dark room for ages and this was a nice
chance to work on some upstream code for a change :)

> > Built for 64 & 32 bit, tested on 64 bit. Survives a kernel build under
> > perf with all tracepoints enabled, and manual inspection of the patched
> > code looks right. But still, lightly tested, YMMV.
> > 
> > Unlike x86 and sparc we just merrily patch the code with no locks etc,
> > as far as I know this is safe, but I'm not really sure what the x86/sparc
> > code is protecting against so maybe it's not.
> 
> Thanks, I'll give it a test on my electra as soon as I get a gcc 4.5.1
> cross compiler working.

Thanks.

cheers



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-11-09  3:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08  4:12 [PATCH] powerpc: Add jump label support Michael Ellerman
2010-11-08 14:18 ` Steven Rostedt
2010-11-09  3:33   ` Michael Ellerman [this message]
2010-11-09  2:35 ` Stephen Rothwell
2010-11-09  3:33   ` Michael Ellerman
2010-11-09  3:41     ` Steven Rostedt
2010-11-09  4:02       ` Michael Ellerman

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=1289273580.21111.193.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=anton@samba.org \
    --cc=davem@davemloft.net \
    --cc=jbaron@redhat.com \
    --cc=kumar.gala@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rostedt@goodmis.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