From: Arjan van de Ven <arjan@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
Olaf Hering <olaf@aepfle.de>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: asm-x86/byteorder.h, CONFIG_X86_BSWAP leaks to userland
Date: Sat, 26 Jul 2008 09:59:01 -0700 [thread overview]
Message-ID: <20080726095901.4a06daf9@infradead.org> (raw)
In-Reply-To: <488B555F.4090709@zytor.com>
On Sat, 26 Jul 2008 12:48:31 -0400
"H. Peter Anvin" <hpa@zytor.com> w
> > I'm not sure if it's time yet to make the bswap ones be exported,
> > as they would no longer be usable for those early machines. X86
> > guys CC:d.
>
> On i386 we still default to i386-compatible binaries; I *think* gcc
> has macros telling you if the user has used -march=i486 etc.
It is also not the kernels job to provide this sort of functionality to
userspace programs. At all. This is gcc/glibc/etc's job.
Rule of thumb: the kernel does not provide code for compiling inside
userspace programs.
(As opposed to providing datastructures that userspace programs can use
to talk to the kernel).
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-07-26 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080726013931.bcc4682d.akpm@linux-foundation.org>
2008-07-26 16:40 ` Fw: asm-x86/byteorder.h, CONFIG_X86_BSWAP leaks to userland Harvey Harrison
2008-07-26 16:48 ` H. Peter Anvin
2008-07-26 16:59 ` Arjan van de Ven [this message]
2008-07-26 18:18 ` H. Peter Anvin
2008-07-26 17:00 ` Fw: " Harvey Harrison
2008-07-21 13:18 Olaf Hering
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=20080726095901.4a06daf9@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=olaf@aepfle.de \
/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