This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] PPC64 enable hp-timing
- From: Tom Gall <tom_gall at vnet dot ibm dot com>
- To: Benjamin Herrenschmidt <benh at kernel dot crashing dot org>
- Cc: Steve Munroe <sjmunroe at us dot ibm dot com>, libc-alpha at sources dot redhat dot com, decimal at us dot ibm dot com
- Date: Mon, 31 Oct 2005 12:50:05 -0600
- Subject: Re: [PATCH] PPC64 enable hp-timing
- References: <20051031015520.8DA241809DA@magilla.sf.frob.com> <1130724509.29054.318.camel@gaston>
Benjamin Herrenschmidt wrote:
On Sun, 2005-10-30 at 17:55 -0800, Roland McGrath wrote:Wouldn't it make a bit more sense to put timebase into sometime else in
/proc? Seems silly to have that value inside of /proc/cpuinfo in the
Well if this is a problem, i386, ia64, and x86_64 have it too. They are
all implemented the same way. sparc64 uses an 8K buffer.In fact all these functions are all looking for just one string and it will
always in reality appear well before the first 4k.
No, on ppc64, it will be at the end.
Course on ppc64 there is
/proc/device-tree/cpus/PowerPC,POWER5@0/timebase-frequency which can get
the same value without having to deal with cpuinfo and it's variable
size. Course the problem with looking in device-tree is that of course
is a config option to the kernel and really valid only on OF hardware.
Still that leads me back to my original observation, shouldn't/couldn't
timebase be put into it's own file in /proc?