From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A6A93C388F9 for ; Sat, 21 Nov 2020 20:10:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3A76A217A0 for ; Sat, 21 Nov 2020 20:10:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=mcrowe.com header.i=@mcrowe.com header.b="YCtwGimE" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728404AbgKUUKg (ORCPT ); Sat, 21 Nov 2020 15:10:36 -0500 Received: from avasout04.plus.net ([212.159.14.19]:56903 "EHLO avasout04.plus.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728402AbgKUUKg (ORCPT ); Sat, 21 Nov 2020 15:10:36 -0500 Received: from deneb ([80.229.24.9]) by smtp with ESMTP id gZDMkgKCprXCcgZDNkWKbU; Sat, 21 Nov 2020 20:10:34 +0000 X-Clacks-Overhead: "GNU Terry Pratchett" X-CM-Score: 0.00 X-CNFS-Analysis: v=2.3 cv=Q+xJH7+a c=1 sm=1 tr=0 a=E/9URZZQ5L3bK/voZ0g0HQ==:117 a=E/9URZZQ5L3bK/voZ0g0HQ==:17 a=kj9zAlcOel0A:10 a=nNwsprhYR40A:10 a=npldXguGAAAA:8 a=uZvujYp8AAAA:8 a=B7kAXZeAyjMtkbLiidkA:9 a=CjuIK1q_8ugA:10 a=Z3hCQHVUXPYA:10 a=sdPHrHSwQQcA:10 a=1MEZn5qd6kv58cYvHi58:22 a=SLzB8X_8jTLwj6mN0q5r:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mcrowe.com; s=20191005; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=kJUCMUyKYyuXqI0RqG9nnmlek9nJ2C9wveJjdVf+oeE=; b=YCtwG imEel+pY+Xbseesw6CbH9C8ipyXIQbXZb1tgr6d2B2O6MNmpHLnEtRTH/vt2PkJHT5vkL96438KCX qXvALJG9gMpyy0ZXAeVUmpOpkB2biIbKtK30cxihhgJhsPcP39N1bmSHCAez6bnT2dO7e6GAQQ1+/ rThjXCYTvfOw3e+M9yKCIqCQGieA1/Yb7+o7I2LIF42J+grr8mbkuWEdFGvisEnGvEWAB1e1VUczk o4iOHYDq5ACFipdbE6rN49tKJ/lx34xtdG15QngxxP//y6IpPI9SH+HvQ/Ilqq30HyeL+e+feD77E Z3xSfgor82LeJxMnIRWXMyWxjbEwQ==; Received: from mac by deneb with local (Exim 4.92) (envelope-from ) id 1kgZDM-0001hG-AT; Sat, 21 Nov 2020 20:10:32 +0000 Date: Sat, 21 Nov 2020 20:10:32 +0000 From: Mike Crowe To: Thomas Gleixner Cc: "mtk.manpages@gmail.com Adhemerval Zanella" , "libc-alpha@sourceware.org" , Linux API Subject: Re: Problems with the new pthread clock implementations Message-ID: <20201121201032.GA5620@mcrowe.com> References: <877dqeo5f5.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877dqeo5f5.fsf@nanos.tec.linutronix.de> User-Agent: Mutt/1.10.1 (2018-07-13) X-CMAE-Envelope: MS4wfAGtLgOr38d223b8NVl+P7/jrz2S4RJJPk2madOZrXDTU4W2UEBgpu9GdK3+tefbByFQkOH23TkeqeH+/wCDI6toXfJIX1bSvRK7GeGTWG9x/Pnrh5KD 35k+JQV6yCIKv7/4KKuaZHpKjW/H6n9YcoNN/RyipQG9x0LfeRqtGImi Precedence: bulk List-ID: X-Mailing-List: linux-api@vger.kernel.org Hi Thomas, On Saturday 21 November 2020 at 20:50:38 +0100, Thomas Gleixner wrote: > On Sat, Nov 21 2020 at 07:59, Michael Kerrisk wrote: > > I've been taking a closer look at the the new pthread*clock*() APIs: > > pthread_clockjoin_np() > > pthread_cond_clockwait() > > pthread_mutex_clocklock() > > pthread_rwlock_clockrdlock() > > pthread_rwlock_clockwrlock() > > sem_clockwait() > > Is there any at least rudimentary specification of these functions and > what they are supposed to do? The short answer is that they are like their "timed" equivalents, but they also accept a clockid. The longer answer is at https://www.austingroupbugs.net/view.php?id=1216 and if you have access to it https://www.opengroup.org/austin/restricted/newapis-p1/Additional_APIs_for_Issue_8-part1-changedpages.pdf HTH. Mike.