From: John Levon <levon@movementarian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /proc/sys/kernel/pointer_size
Date: Wed, 8 Jan 2003 22:40:06 +0000 [thread overview]
Message-ID: <20030108224006.GA47765@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0301081300200.1497-100000@home.transmeta.com>
On Wed, Jan 08, 2003 at 01:03:14PM -0800, Linus Torvalds wrote:
> You should certainly see it in "uname -a" output, for example.
Hrmph. Actually we can take it from the ELF headers of the vmlinux file
that gets passed in I suppose. Along with a uname hack for when there's
no vmlinux available...
> The same is true of kernel modules - 32-bit kernel modules do not work at
> all when the kernel is 64-bit.
Modules aren't in userspace.
> 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.
I don't see what's stupid about a 32-bit binary on a system where all of
user-space is 32-bit. But it doesn't matter.
regards
john
--
"CUT IT OUT FACEHEAD"
- jeffk
next prev parent reply other threads:[~2003-01-08 22:31 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
2003-01-08 22:40 ` John Levon [this message]
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=20030108224006.GA47765@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox