From: Anton Blanchard <anton@samba.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ingo Oeser <ioe-lkml@rameria.de>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Add prctl to change endian of a task
Date: Tue, 4 Apr 2006 08:36:20 +1000 [thread overview]
Message-ID: <20060403223620.GC4704@krispykreme> (raw)
In-Reply-To: <1143989770.29060.28.camel@localhost.localdomain>
Hi,
> Abuse is a possible problem but you can deal with that. If you don't
> inherit endian changes then the problem doesn't occur. If you must
> inherit them then drop the inheritance when an suid/sgid exec occurs as
> we do with some other properties.
Yeah dropping it on exec makes sense to me.
> Can you explain however why you can't do this simply by using a binary
> magic number in the executable to indicate which endian it is, or do you
> really need to flip it ?
The aim is not to implement little endian binaries but to assist
running portions of code in little endian mode. The thought is we could
hook up qemu to it and avoid having to byteswap.
While ppc has byteswap integer loads it does not have byteswap floating
point loads and a byteswap involves loading into the integer unit,
performing the byteswap, storing to a temporary location and loading
into the floating point unit. Rather slow.
Anton
next prev parent reply other threads:[~2006-04-03 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 22:29 [PATCH] Add prctl to change endian of a task Anton Blanchard
2006-04-02 14:37 ` Ingo Oeser
2006-04-02 14:56 ` Alan Cox
2006-04-03 22:36 ` Anton Blanchard [this message]
2006-04-03 22:40 ` David S. Miller
2006-04-06 5:13 ` Paul Mackerras
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=20060403223620.GC4704@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ioe-lkml@rameria.de \
--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.