public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] 64-bit kernel on a 32-bit installation
Date: Tue, 9 Jun 2009 16:44:38 -0700	[thread overview]
Message-ID: <5bdc1c8b0906091644t5c6601ddn81f7944cacc049be@mail.gmail.com> (raw)

Hi,
   I lurk on the LKML, say hi once in awhile, ask a question once in
awhile, and try to read at least the interesting to a non-programmer
posts. I was curious about this one that came up today. Seems like
this is a natural for Gentoo.

   I have a Gentoo 64-bit setup but have had lots of troubles over the
years (far less now though) with web media and other things that need
to be more Windows compatible. (I do audio work with my Gentoo boxes -
interface to studios and a few bands, etc) I've found that my 32-bit
Gentoo installations have been more compatible than 64-bit. Outside
stuff like Java is better. In general when I have a problem I wonder
if it's because I'm running 64-bit.

   How would one go about building a 64-bit kernel on a 32-bit machine
with Gentoo? I presume that's mostly just how I configure the kernel,
along with maybe some cross-compile options? Are there any projects
going on in this area where I might become a test case? Wiki? Docs?

   Do others see value - getting 64-bit memory management, new CPU
flags, etc., but keeping the apps 32-bit for compatibility?

Take care,
Mark

<SNIP>
On Tue, 9 Jun 2009, H. Peter Anvin wrote:
>
> A major problem is that distros don't seem to be willing to push 64-bit
> kernels for 32-bit distros.  There are a number of good (and
> not-so-good) reasons why users may want to run a 32-bit userspace, but
> not running a 64-bit kernel on capable hardware is just problematic.

Yeah, that's just stupid. A 64-bit kernel should work well with 32-bit
tools, and while we've occasionally had compat issues (the intel gfx
people used to claim that they needed to work with a 32-bit kernel because
they cared about 32-bit tools), they aren't unfixable or even all _that_
common.

And they'd be even less common if the whole "64-bit kernel even if you do
a 32-bit distro" was more common.

The nice thing about a 64-bit kernel is that you should be able to build
one even if you don't in general have all the 64-bit libraries. So you
don't need a full 64-bit development environment, you just need a compiler
that can generate code for both (and that should be the default on x86
these days).

                       Linus
<SNIP>



             reply	other threads:[~2009-06-09 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 23:44 Mark Knecht [this message]
2009-06-10  5:35 ` [gentoo-user] Re: 64-bit kernel on a 32-bit installation ABCD
2009-06-10  5:58 ` Nikos Chantziaras

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=5bdc1c8b0906091644t5c6601ddn81f7944cacc049be@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.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