ClockId(), ClockId_r()

Get the CPU-time clock ID for a given process and thread


#include <sys/neutrino.h>
#include <inttypes.h>

extern int ClockId( pid_t pid, 
                    int tid ); 

extern int ClockId_r( pid_t pid, 
                      int tid ); 


BlackBerry 10.0.0


The ID of the process that you want to get the clock ID for. If this argument is zero, the ID of the process making the call is assumed.
The ID of the thread that you want to get the clock ID for, or 0 to get clock ID for the process as a whole.



Use the -l c option to qcc to link against this library. This library is usually included automatically.


The ClockId() and ClockId_r() kernel calls retrieve an integer CPU-time clock ID that you can pass as a clockid_t to ClockTime(). When you pass this clock ID to ClockTime(), that function returns (in the location pointed to by old) the number of nanoseconds that the specified thread of the specified process has executed.

The ClockId() and ClockId_r() functions are identical except in the way they indicate errors. See the Returns section for details.

Instead of using these kernel calls directly, consider calling clock_getcpuclockid() or pthread_getcpuclockid().

If the tid is zero, ClockTime() gives you the number of nanoseconds that the process as a whole has executed. On an SMP box, this number may exceed the realtime number of nanoseconds that have elapsed because multiple threads in the process can run on several CPUs at the same time.

Blocking states:

This call doesn't block.


An integer that can be passed to ClockTime(). If an error occurs, the function returns -1 and sets errno .
An integer that can be passed to ClockTime(). This function does NOT set errno. If an error occurs, the function returns the negative of a value from the Errors section.


The pid and/or tid don't exist.


Here's how you can determine how busy a system is:

id = ClockId(1, 1);
for( ;; ) {
    ClockTime(id, NULL, &start);
    ClockTime(id, NULL, &stop);
    printf("load = %f%%\n", (1000000000.0 - (stop-start)) / 10000000.0);


QNX Neutrino

Cancellation point No
Interrupt handler No
Signal handler Yes
Thread Yes

Last modified: 2014-06-24

Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus