From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: levon@movementarian.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /proc/sys/kernel/pointer_size
Date: Wed, 08 Jan 2003 14:37:52 -0800 (PST) [thread overview]
Message-ID: <20030108.143752.53085708.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301081300200.1497-100000@home.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Wed, 8 Jan 2003 13:03:14 -0800 (PST)
On Wed, 8 Jan 2003, John Levon wrote:
> What other ways ? Dave M reasonably argued it wasn't part of the
> architecture's ABI, so did not have a place in the headers.
You should certainly see it in "uname -a" output, for example.
Doesn't tell you the kernel pointer size. We fake the uname
output when a process runs as PERS_LINUX_32BIT which is what
we use to trick 'configure' and other build programs in order to
build 32-bit apps properly.
Compile oprofile for the proper architecture if you do it yourself, and
complain to the vendor if the vendor is stupid enough to supply a 32-bit
oprofile with a 64-bit kernel.
There is _no_ excuse to bloat the kernel for user mistakes.
There simply is no fully usable 64-bit userland on some of these
platforms.
next prev parent reply other threads:[~2003-01-08 22:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 19:59 [PATCH] /proc/sys/kernel/pointer_size John Levon
2003-01-08 20:28 ` Linus Torvalds
2003-01-08 20:52 ` John Levon
2003-01-08 21:03 ` Linus Torvalds
2003-01-08 22:37 ` David S. Miller [this message]
2003-01-08 22:40 ` John Levon
2003-01-11 9:18 ` Kai Henningsen
2003-01-08 22:34 ` David S. Miller
2003-01-08 23:04 ` Linus Torvalds
2003-01-08 23:03 ` David S. Miller
2003-01-09 0:02 ` Linus Torvalds
2003-01-09 0:03 ` David S. Miller
2003-01-09 4:00 ` Daniel Jacobowitz
2003-01-09 4:31 ` David S. Miller
2003-01-09 5:23 ` William Lee Irwin III
2003-01-09 23:09 ` Bill Davidsen
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=20030108.143752.53085708.davem@redhat.com \
--to=davem@redhat.com \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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