From: Andi Kleen <ak@suse.de>
To: Richard Henderson <rth@twiddle.net>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: in-kernel linking issues
Date: 15 Nov 2002 05:13:23 +0100 [thread overview]
Message-ID: <p73wunfv5b0.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Richard Henderson's message of "14 Nov 2002 23:41:01 +0100"
Richard Henderson <rth@twiddle.net> writes:
> These will affect at least Alpha, IA-64, and MIPS.
>
> (3) Alpha and MIPS64 absolutely require that the core and init allocations
> are "close" (within 2GB). I don't see how this can be guaranteed with
> two different vmalloc calls.
In x86-64 (and I think sparc64) the modules (both data and code) also need
to be within 2GB of the main kernel code. This is done to avoid needing
a GOT for calls between main kernel and modules. In the old module code that
is done with a custom module_map() function. I have not looked yet on how
that could be implemented in the new code.
-Andi
next parent reply other threads:[~2002-11-15 4:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021114143701.A30355@twiddle.net.suse.lists.linux.kernel>
2002-11-15 4:13 ` Andi Kleen [this message]
2002-11-15 4:21 ` in-kernel linking issues Richard Henderson
2002-11-15 8:44 ` Rusty Russell
2002-11-15 10:29 ` Andi Kleen
2002-11-15 12:51 ` Richard Henderson
2002-11-15 13:16 ` Russell King
2002-11-15 22:30 ` Richard Henderson
2002-11-15 21:21 ` Rusty Russell
2002-11-15 22:22 ` Richard Henderson
2002-11-15 22:45 ` Rusty Russell
2002-11-15 23:47 ` Richard Henderson
2002-11-16 6:19 ` Rusty Russell
2002-11-18 16:46 ` Kai Germaschewski
2002-11-19 6:26 ` Rusty Russell
2002-11-14 22:37 Richard Henderson
2002-11-16 5:47 ` Rusty Russell
2002-11-16 22:51 ` Richard Henderson
[not found] ` <20021117130132.AA5352C058@lists.samba.org>
2002-11-17 20:59 ` Richard Henderson
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=p73wunfv5b0.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=rusty@rustcorp.com.au \
/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