From: Arnd Bergmann <arnd@arndb.de>
To: discuss@x86-64.org
Cc: "Jin, Gordon" <gordon.jin@intel.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [discuss] [PATCH x86_64]: Setup PER_LINUX32 on x86_64
Date: Wed, 10 Nov 2004 10:51:37 +0100 [thread overview]
Message-ID: <200411101051.37702.arnd@arndb.de> (raw)
In-Reply-To: <8126E4F969BA254AB43EA03C59F44E84BBECA2@pdsmsx404>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Dinsdag 02 November 2004 09:47, Jin, Gordon wrote:
> On x86_64, PER_LINUX32 is not setup but used by syscall personality and uname.
> This patch sets PER_LINUX32 when x86 binary loaded so it can be used correctly.
> - Set personality to PER_LINUX32 when x86 binary loaded.
> - Set personality to PER_LINUX when x86_64 binary loaded.
> - Use sys32_personality instead of sys_personality.
> - Add sys32_newuname() for syscall newuname.
> - Remove the unnecessary check for PER_LINUX32 in sys_uname().
That behavior would be significantly different from the current one,
which is also used on all other biarch architectures. This probably
breaks lots of user setups.
I also think the current behavior is the right one. For things like
configure, you need a way to set the uname independent of the binary
format of your shell. Another example is building rpm packages
on a mixed system, where should be able to set the personality
to decide which target architecture to build for.
Arnd <><
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-11-10 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 8:47 [PATCH x86_64]: Setup PER_LINUX32 on x86_64 Jin, Gordon
2004-11-10 9:51 ` Arnd Bergmann [this message]
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=200411101051.37702.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=discuss@x86-64.org \
--cc=gordon.jin@intel.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.