mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: [PATCH] /proc/sys/kernel/pointer_size
Date: Wed, 8 Jan 2003 20:52:20 +0000	[thread overview]
Message-ID: <20030108205220.GB35912@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0301081222430.5369-100000@home.transmeta.com>

On Wed, Jan 08, 2003 at 12:28:23PM -0800, Linus Torvalds wrote:

> doesn't change suddenly on the machine, there's no point at all in doing
> something like this and exporting it through proc, when the information is
> perfectly available in other ways

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.

> or could even be a user program config file option.

Eww.

> Quite frankly, just compile oprofile for the architecture and be done with 
> it. Or add a command line option. Don't add stupid bloat to the kernel 
> because somebody is silly enough to care about a 32-bit oprofile working 
> with a 64-bit kernel. 

It's not silly, it's a necessity on architectures like pa-risc, sparc64,
ppc64, etc. where pointers are 32 bit in userspace. OProfile simply
cannot work at all on such systems without being able to figure out the
units of the oprofile kernel buffer.

We could force the oprofile kernel buffer to always be u64s but that
just eats unnecessary space and time on x86.

So, what solution do you suggest instead ?

regards
john

-- 
"CUT IT OUT FACEHEAD"
	- jeffk

  reply	other threads:[~2003-01-08 20:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 19:59 John Levon
2003-01-08 20:28 ` Linus Torvalds
2003-01-08 20:52   ` John Levon [this message]
2003-01-08 21:03     ` Linus Torvalds
2003-01-08 22:37       ` David S. Miller
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=20030108205220.GB35912@compsoc.man.ac.uk \
    --to=levon@movementarian.org \
    --cc=davem@redhat.com \
    --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

all inboxes | Powered by JetHome®