public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Paul Mackerras <paulus@samba.org>,
	akpm@osdl.org, anton@samba.org, linux-kernel@vger.kernel.org,
	jk@blackdown.de
Subject: Re: [PATCH] ppc64: Fix PER_LINUX32 behaviour
Date: Wed, 8 Jun 2005 20:49:48 +0200	[thread overview]
Message-ID: <200506082049.51707.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0506081022030.2286@ppc970.osdl.org>

On Middeweken 08 Juni 2005 19:24, Linus Torvalds wrote:

> I think this is a feature, not a bug, and I suspect you just broke
> compiling a 64-bit kernel by default on ppc64.
> 
> Dammit, the system _is_ ppc64. The fact that the uname binary is not is
> neither here nor there. It's like x86 that reports i386/i486/.. depending 
> on what the machine is. If uname wants to make it clear that uname has 
> been compiled for 32-bit ppc, then it can damn well output "ppc" on its 
> own without asking the kernel what the kernel is.

The whole point of the LINUX32 personality is to mangle the output of
uname, it doesn't do anything else on the architectures I have worked 
with (s390, x86_64 and ppc64).

Even with the patch, the normal operation would be to use PER_LINUX
for everything, so the kernel build works as expected unless you pass
the obsolete "fakeppc" boot parameter.

With the LINUX32 personality, you can build 32 bit binaries through
autoconf, rpmbuild, or the kernel without pretending to be
cross-compiling. It may not be the best solution, but people seem to
rely on it and the patch brings ppc64 in line with how it works on
the other architectures.

	Arnd <><

  reply	other threads:[~2005-06-08 19:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 11:59 [PATCH] ppc64: Fix PER_LINUX32 behaviour Paul Mackerras
2005-06-08 17:24 ` Linus Torvalds
2005-06-08 18:49   ` Arnd Bergmann [this message]
2005-06-08 19:19     ` David S. Miller
2005-06-08 20:45       ` Olaf Hering
2005-06-08 20:45   ` Andreas Schwab
2005-06-08 20:54     ` Juergen Kreileder
2005-06-08 22:40       ` Andreas Schwab
2005-06-09  7:02         ` Juergen Kreileder
2005-06-08 23:12   ` Paul Mackerras
2005-06-08 23:16     ` David S. Miller
2005-06-11 11:24       ` Andi Kleen
2005-06-08 23:28     ` Linus Torvalds
2005-06-08 23:12   ` Benjamin Herrenschmidt
     [not found] <20050608.121950.104038734.davem@davemloft.net.suse.lists.linux.kernel>
2005-06-08 20:50 ` Marcus Meissner

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=200506082049.51707.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=jk@blackdown.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=torvalds@osdl.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