On Thu, Jun 29, 2006 at 12:55:13PM +0200, Arjan van de Ven wrote:
> On Thu, 2006-06-29 at 12:48 +0200, Jes Sorensen wrote:
> > Alan Cox wrote:
> > > Ar Iau, 2006-06-29 am 05:37 -0400, ysgrifennodd Jes Sorensen:
> > >> You have my vote for that one. Anything else is just going to cause
> > >> those broken userapps to continue doing the wrong thing. We should
> > >> really do this on all archs though.
> > >
> > > No need, all current mainstream architectures expose a constant user HZ.
> >
> Hi,
>
> > But you are still going to have the issue where someone installs their
> > own kernel and apps will break because of this?
>
> to answer that question with one word: no.
>
> read what Alan said: the HZ exposed to userspace is *constant*. For
> example, the i386 user visible HZ is 100, even if the kernel runs at a
> HZ of 250 or 1000.... Just when a HZ value gets exposed to userspace,
> it's transformed into a HZ=100 based value.
>
> And that's not a distribution thing, that's the kernel.org kernel
> honoring the stable-userspace-interface contract, and common sense..
So does i386 convert the return value of the times(2) call to user
hertz? On IA64, it returns the value in internal clock ticks, and
then when a program uses the value in param.h, it gets it wrong now,
because internal HZ is now 250.
So is times() is broken in IA64, or is this an exception to Alan's
statement?
jeremy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
