From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) by sourceware.org (Postfix) with ESMTPS id 26A31384783A for ; Fri, 2 Jul 2021 13:53:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 26A31384783A Received: by mail-pg1-x531.google.com with SMTP id d12so9603089pgd.9 for ; Fri, 02 Jul 2021 06:53:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=OTRSFIG9NSJU6hDboAl5H0lKf5zs2SXpyC0TB4qBLkk=; b=XUtdItIru5xMpzy9rNSt75CtBVawuFHpvYkows6pFYHVinmOeZCj/Ggqj3VQgS5ulR jMAhD+ttcsI+XFNCWS+HBNu4CYjGvBDSzhAmKXK0jHgtLiMGknXdCBjLLRlmmu592jsC w/qhxQ5QvJa3GHxbFSrboNyjHZKx1TdSAks4S3K3Syyol1OXud76FhDSg31KsYyJIrpc /LDeFKIahu2W2n+hEnlBjkv/4QDbzTStXOuQ7UUdnFHQJaxXNkILp3h1MnMXkNLoMlGx WDiAqTxNY3NUCXqR7zbWxowUlVvxUcz5fx+jHcMPpwdYy62jgGO1uOIFtAdPJyvrHiEG hwPQ== X-Gm-Message-State: AOAM530yuSpOa5l/w9UWIwEv2WyqIvDUl+pg2vklNXJfcYNoNSqfXL4X PJfwQpvZoSFgDJtMPqVFSyKwFKkte6knNQ== X-Google-Smtp-Source: ABdhPJwrk/4iprlyt+1PDA34I62ahnXKkXDwNf/NPwNADxJl1vXiDYy5IOkTQzMMKm5vhnmqi9iIwg== X-Received: by 2002:aa7:9727:0:b029:304:3644:2771 with SMTP id k7-20020aa797270000b029030436442771mr5424095pfg.73.1625233993072; Fri, 02 Jul 2021 06:53:13 -0700 (PDT) Received: from [192.168.1.108] ([177.194.59.218]) by smtp.gmail.com with ESMTPSA id x5sm3701864pfu.116.2021.07.02.06.53.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 02 Jul 2021 06:53:12 -0700 (PDT) Subject: Re: aarch64 lacks HP_TIMING support in glibc To: Wilco Dijkstra , Rafael Eduardo Ruviaro Christ , 'GNU C Library' References: From: Adhemerval Zanella Message-ID: <06b1464a-cefe-0e57-30e4-634c5b03c2d1@linaro.org> Date: Fri, 2 Jul 2021 10:53:10 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2021 13:53:15 -0000 On 02/07/2021 10:13, Wilco Dijkstra via Libc-alpha wrote: > You could propose a RFC to improve the clock_getres implementation and see > what people say. It might help if you have use cases where knowing the exact > resolution is essential. > I really prefer if we avoid trying to hack this on userspace and let the kernel handle it instead, specially if requires a arch-specific implementation. I think it is really unlikely that we would get a better resolution in userspace that kernel can't provide more efficiently.