From: Andreas Schwab <schwab@suse.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, 08 Jun 2005 22:45:23 +0200 [thread overview]
Message-ID: <jey89kbmsc.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0506081022030.2286@ppc970.osdl.org> (Linus Torvalds's message of "Wed, 8 Jun 2005 10:24:59 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> On Wed, 8 Jun 2005, Paul Mackerras wrote:
>>
>> * uname(2) doesn't respect PER_LINUX32, it returns 'ppc64' instead of 'ppc'
>
> I think this is a feature, not a bug, and I suspect you just broke
> compiling a 64-bit kernel by default on ppc64.
The uname syscall that Paul is referring to (__NR_olduname) isn't actually
used nowadays any more. The current uname syscall (__NR_uname, which is
implemented by ppc64_newuname) already translates ppc64 to ppc depending
on the personality.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-06-08 20:45 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
2005-06-08 19:19 ` David S. Miller
2005-06-08 20:45 ` Olaf Hering
2005-06-08 20:45 ` Andreas Schwab [this message]
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=jey89kbmsc.fsf@sykes.suse.de \
--to=schwab@suse.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