linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: help with ppc sections?
Date: Fri, 27 Jul 2007 12:55:52 -0600	[thread overview]
Message-ID: <46AA3FB8.8030301@nortel.com> (raw)
In-Reply-To: <fa686aa40707261255x23b06ff4y5fe1527f72c09c5b@mail.gmail.com>

Grant Likely wrote:

> Mild question; What the *@*#^$! are you doing trying to backport to a
> 2 year old kernel?!?  :-)

That's what happens in the embedded space.  It's the current version 
from our distro vendor.  It's also the version that all our different 
board suppliers could agree to provide support for.

Of course, it's also a royal pain.

>> Unfortunately for me, ppc doesn't have a ".section" line in that macro,
>> so I'm at a bit of a loss.

> Just add the section.  Should be trivial to do.  You might have to add
> it to the linker script as well.

I've done the linker script part already.  As for the processor.h bit, 
does this seem reasonable?  It seems to do the trick based on the 
function addresses, but I may be missing something and I haven't 
actually booted it yet.

The ppc64 version appends ',"a"' to the kprobes.text section line.  Is 
this needed here as well?  Could someone elaborate on exactly what its 
purpose is?

Thanks,

Chris


Index: linux-ias/include/asm-ppc/processor.h
===================================================================
--- linux-ias.orig/include/asm-ppc/processor.h
+++ linux-ias/include/asm-ppc/processor.h
@@ -38,6 +38,13 @@

  #define _GLOBAL(n)\
  	.stabs __stringify(n:F-1),N_FUN,0,0,n;\
+	.section ".text"; \
+	.globl n;\
+n:
+
+#define _KPROBE(n)\
+	.stabs __stringify(n:F-1),N_FUN,0,0,n;\
+	.section ".kprobes.text","a"; \
  	.globl n;\
  n:

  reply	other threads:[~2007-07-27 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 19:12 help with ppc sections? Chris Friesen
2007-07-26 19:55 ` Grant Likely
2007-07-27 18:55   ` Chris Friesen [this message]
2007-07-31 16:38     ` Segher Boessenkool
2007-08-08 16:24 ` help with ppc sections -- no luck, any ideas? Chris Friesen

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=46AA3FB8.8030301@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.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).