From: Andi Kleen <ak@suse.de>
To: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD64: 64 bit kernel 32 bit userland - some pending questions
Date: 06 Jun 2006 12:42:30 +0200 [thread overview]
Message-ID: <p73lksazht5.fsf@verdi.suse.de> (raw)
In-Reply-To: <20060606093456.GL4552@cip.informatik.uni-erlangen.de>
Thomas Glanzmann <sithglan@stud.uni-erlangen.de> writes:
> Hello everyone,
> I would like to use an AMD64 Opteron System with a 64 bit Linux Kernel,
> but a 32 bit userland (Debian Sarge). I have a few questions about this:
The main caveat is that iptables and ipsec need 64bit executables
to be set up. The rest should work.
>
> - Is it possible to give the userland 3Gbyte virtual address
> space (default for 2.4 and 2.6).
The default is 4GB, but you can get 3GB by running it under linux32 --3gb
> But give the Kernel a 64 bit
> virtual address space so that I get more than 1 Gbyte physical
> Memory into LOWMEM - say I want 8 Gbyte - without using HIGHMEM
The 64bit kernel never uses highmem.
> - What is the easiest way to build a 64 bit kernel on a 32 bit
> Debian sarge. Are there crosscompiler packages available? Are
> there any guides on this?
If all fails you can get a cross compiler from crosstool.
Then normal kernel compilation command with
make ... ARCH=x86_64 CROSS_COMPILE=x86_64-linux-
-Andi
next prev parent reply other threads:[~2006-06-06 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 9:34 AMD64: 64 bit kernel 32 bit userland - some pending questions Thomas Glanzmann
2006-06-06 10:42 ` Andi Kleen [this message]
2006-06-06 10:49 ` Thomas Glanzmann
2006-06-06 11:51 ` Rafael J. Wysocki
2006-06-06 11:55 ` Andi Kleen
2006-06-06 11:56 ` Marcus Meissner
2006-06-06 12:11 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 3:11 Albert Cahalan
2006-06-07 4:08 ` H. Peter Anvin
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=p73lksazht5.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sithglan@stud.uni-erlangen.de \
/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