From: Sam Ravnborg <sam@ravnborg.org>
To: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: use ELF sections for get_wchan()
Date: Wed, 19 Nov 2003 06:53:32 +0100 [thread overview]
Message-ID: <20031119055332.GA934@mars.ravnborg.org> (raw)
In-Reply-To: <20031119031337.GM22764@holomorphy.com>
On Tue, Nov 18, 2003 at 07:13:37PM -0800, William Lee Irwin III wrote:
> willy said I should use .sched.text instead of .text.sched; this fixes
> it up to do that.
Hi wli,
how about utilising asm-generic/vmlinux.h.S now that you are touching so
many .lds files?
Something like the attached could be used?
That will simplify and consolidate the the .lds files, but full
flexibility remains.
I noticed that there were small diferences between the individual
architectures, but specifying only content of the section should allow
it to be used all over.
Sam
===== include/asm-generic/vmlinux.lds.h 1.8 vs edited =====
--- 1.8/include/asm-generic/vmlinux.lds.h Thu Jun 12 02:40:10 2003
+++ edited/include/asm-generic/vmlinux.lds.h Wed Nov 19 06:48:40 2003
@@ -45,6 +45,15 @@
*(__ksymtab_strings) \
}
+#define TEXT_CONTENT \
+ _stext = .; \
+ *(.text) \
+ __schduling_functions_start_here = .; \
+ *(.sched.text) \
+ __scheduling_functions_end_here = .; \
+ *(.fixup) \
+ *(.gnu.warning)
+
#define SECURITY_INIT \
.security_initcall.init : { \
__security_initcall_start = .; \
next prev parent reply other threads:[~2003-11-19 5:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 7:44 use ELF sections for get_wchan() William Lee Irwin III
2003-11-18 8:43 ` Russell King
2003-11-18 8:45 ` William Lee Irwin III
2003-11-18 8:50 ` William Lee Irwin III
2003-11-19 3:13 ` William Lee Irwin III
2003-11-19 5:53 ` Sam Ravnborg [this message]
2003-11-19 6:19 ` William Lee Irwin III
2003-11-20 20:28 ` Anton Blanchard
2003-11-20 20:50 ` William Lee Irwin III
2003-11-20 22:55 ` William Lee Irwin III
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=20031119055332.GA934@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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