lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A1D6E71.90602@nortel.com>
Date:	Wed, 27 May 2009 10:46:41 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	linux-kernel@...r.kernel.org, tglx@...utronix.de
Subject: linux missing support for _POSIX_THREAD_CPUTIME?

Hi all,

POSIX defines optional support for clock ID values obtained by invoking
pthread_getcpuclockid().  When passed to clock_gettime(), this allows
the caller to request the CPU-time clock of an arbitrary thread within
the same process as the caller.

It appears that linux doesn't support this functionality--is that
correct?  Is there any plan to enable this?

Is there any current way to obtain the runtime of a particular thread
without knowing its tid (since the thread_id to tid mapping is known
only to glibc)?

Thanks,

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ