thanks for the rant. most entertaining. for what its worth, i wasn't
trolling.
>2.2.xx i386 as shipped by Linus
>2.4.xx i386 with HZ modified
(i assume you mean 2.4.xx i386 as shipped by Linus)
>Come on, write the code if you think it's so easy.
>You get bonus points for supporting 2.0.xx kernels
>and the IA-64 kernel with that same executable.
i suspect you're confusing me with someone else.
in either case, for ELF executables, the kernel puts the CLOCKS_PER_TICK on
the stack when loading an elf binary.
this is defined to be HZ on all platforms except ia32 where its set to
100. one would hope that if you redefine HZ to something else, you also
remember to redefine CLOCKS_PER_TICK to that same value too.
my tree uses CLOCKS_PER_TICK set to HZ for x86 too. i also use a tree with
HZ set to 1000 for a packet-latency-inducer packet-scheduler i use.
the following code determines the value of CLOCKS_PER_TICK in a reliable
manner on the hosts i have here (2.4.xx, 2.5.xx, ia32):
i don't have any alpha or ia64 boxes here, but i'm confident it'll still
give you the correct result.
--
#include <stdio.h>
#include <unistd.h>
#define AT_CLKTCK 17 /* Frequency of times() */
int main(int argc, char *argv[])
{
int i = 0;
fprintf(stderr,"sysconf says %u ticks per
second\n",sysconf(_SC_CLK_TCK));
/* loop through command-line and args */
while (argv[i] != NULL)
i++;
/* loop through environment variables */
i++;
while (argv[i] != NULL)
i++;
/* now at elf variables */
i++;
while (argv[i] != NULL) {
if ((int)argv[i] != AT_CLKTCK) {
fprintf(stderr,"(elf header entry %d has
value %d)\n",
(int)argv[i], (int)(argv[(i+1)]));
} else {
/* got it */
fprintf(stderr,"eureka, elf header says we
have %d ticks per second\n",(int)argv[(i+1)]);
break;
}
i += 2;
}
}
--
the code doesn't work on a 2.2.16 box here, given 2.2.16 doesn't have
AT_CLKTCK, but i believe that is incidental to this discussion.
cheers,
lincoln.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/