From: Arnd Bergmann <arnd@arndb.de>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: generalize/fix wchan calculation via ELF sections
Date: Wed, 31 Mar 2004 13:30:11 +0200 [thread overview]
Message-ID: <200403311330.12089.arnd@arndb.de> (raw)
In-Reply-To: <20040331073539.GX791@holomorphy.com>
On Wednesday 31 March 2004 09:35, William Lee Irwin III wrote:
> Basically, I'm looking to see if I flubbed the patch and may not have
> swept all arches properly, or whether arch maintainers dislike whatever
> aspects of it since it goes poking around their code. Whatever kind of
> feedback may be relevant wrt. methods/cleanliness/etc. is also good.
> Index: sched-2.6.5-rc3/arch/i386/kernel/vmlinux.lds.S
> ===================================================================
> --- sched-2.6.5-rc3.orig/arch/i386/kernel/vmlinux.lds.S 2004-03-29 19:25:34.000000000 -0800
> +++ sched-2.6.5-rc3/arch/i386/kernel/vmlinux.lds.S 2004-03-30 23:25:36.000000000 -0800
> @@ -16,6 +16,9 @@
> _text = .; /* Text and read-only data */
> .text : {
> *(.text)
> + __scheduling_functions_start_here = .;
> + *(.sched.text)
> + __scheduling_functions_end_here = .;
> *(.fixup)
> *(.gnu.warning)
> } = 0x9090
No objections, just an idea: It might be good to put the vmlinux.lds.S
changes into a macro in include/asm-generic/vmlinux.lds.h. IIRC, that's
what that file was introduced for, although it's not used for many things
so far.
Arnd <><
next prev parent reply other threads:[~2004-03-31 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 7:35 generalize/fix wchan calculation via ELF sections William Lee Irwin III
2004-03-31 8:03 ` Andi Kleen
2004-03-31 8:13 ` William Lee Irwin III
2004-03-31 11:30 ` Arnd Bergmann [this message]
2004-03-31 13:10 ` Matthew Wilcox
2004-04-01 7:17 ` David S. Miller
2004-04-01 7:58 ` Anton Blanchard
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=200403311330.12089.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arch@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