Received: by 2002:a05:6a10:87d6:0:0:0:0 with SMTP id g22csp1100040pxr; Mon, 11 Apr 2022 15:17:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxJPq/pfwVoJbI55ROfhqoENcFxnLuC+sI0IbYyJ6KVgImSyEc4aVFm72aCEEKC9QX+MoKr X-Received: by 2002:a05:6a00:130e:b0:4f3:9654:266d with SMTP id j14-20020a056a00130e00b004f39654266dmr34587360pfu.59.1649715453050; Mon, 11 Apr 2022 15:17:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649715453; cv=none; d=google.com; s=arc-20160816; b=jtg7F5aXWkdny7tienVS/9Zx3w7YUpOInnQjUBG6Hb6BQJk6sSMsirX6u79iiNbvUI ybNyklWco+yu3rQcD/wsGMmUafAaDbAJi1cepJetMD7NyY4hFctHhjtN9pMNXBnQM/Q+ 3vZpV4+GfCfuCVBAaY4ECGvilhtvtx+J6Z6vTgAYbk4IF2oFyCd41Sr3xi4bbC+/kdh7 r73sY1Md422GlJ9n2zS01LisZZNkAJ28iDvEywl24xf9FNGLHTIn60SCw2mkWZy8dvzD od+vVqyQRBuXMoKAhd6n552Sn6NpY3VcEGph/08qk6hIlRQC1bAzedD2Kpt7Z2r10bSW +s2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=I6zxkOx/mC7wvk4Gsn1jwFNXEhXgfgnf3fm3eSnaMTE=; b=ghjRkYHrbDvStDkseXbj2+HVjJXuhT5JWAJA2qUeZBolxpnz7AqW4683Wc21qr3R+g uACyodpmbpiRZXP+gC/i9uj0p+RkdolvVptkPjXbSGEhlcVUaMbkZ8Fkdqd2D4AonZQK elWKa0rv2or1C9su22cti5bCPKiS3qQGzqms1yxJ8x6sQA6aqCwRkdcB7AGCJkv9VvYv kgZzotsnnm6XcbOHhnSQvuVbPKWJXzjK2RF8f/LfkRncUroTMgN0vqBYlgBpiDJTLb+r Zhj7MaU2Dr0aW55XIE8LlM9N+OFowZ2jjjbADU8hY5qyCny5JBV6/ryJ0Io8ngTjDZqK cA3w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=NrFXxny0; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k191-20020a6384c8000000b0039d6a49d79fsi1049269pgd.4.2022.04.11.15.17.06; Mon, 11 Apr 2022 15:17:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=NrFXxny0; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235181AbiDJVlE (ORCPT + 99 others); Sun, 10 Apr 2022 17:41:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35988 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229846AbiDJVlD (ORCPT ); Sun, 10 Apr 2022 17:41:03 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CD9563B551; Sun, 10 Apr 2022 14:38:50 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 125B1B80EC8; Sun, 10 Apr 2022 21:38:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4BB8FC385A5; Sun, 10 Apr 2022 21:38:47 +0000 (UTC) Authentication-Results: smtp.kernel.org; dkim=pass (1024-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="NrFXxny0" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1649626721; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=I6zxkOx/mC7wvk4Gsn1jwFNXEhXgfgnf3fm3eSnaMTE=; b=NrFXxny0IyP3/c19IXFJeNYIjz9bo5HSb8TVdyJF71GUw5newhJgJE4hQONP85hku3z+3A D1EiTkXt9Ia/qCihahanmaYzNyMmtPHjAC4fTqzaMqO9Uc+Bn0RphKT2gO/5h2Q6aOlLOx 9Y1pJog9We26rTE2mdLszVwcT02CsHY= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 9f3ca50a (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Sun, 10 Apr 2022 21:38:40 +0000 (UTC) Received: by mail-yw1-f175.google.com with SMTP id 00721157ae682-2e5e31c34bfso146567937b3.10; Sun, 10 Apr 2022 14:38:39 -0700 (PDT) X-Gm-Message-State: AOAM530SacCI04STO32DNppJM6Jgz4w2Ri76AdBz4gRmvb5KDx/qMmwf Oj72Ldm1UJA8KGHtfFpHEDkhelmdPFXLxaa8zjk= X-Received: by 2002:a81:6a84:0:b0:2ec:c59:9d22 with SMTP id f126-20020a816a84000000b002ec0c599d22mr3204724ywc.499.1649626717509; Sun, 10 Apr 2022 14:38:37 -0700 (PDT) MIME-Version: 1.0 References: <20220408182145.142506-1-Jason@zx2c4.com> <87wnfxhm3n.ffs@tglx> <877d7whd29.ffs@tglx> In-Reply-To: <877d7whd29.ffs@tglx> From: "Jason A. Donenfeld" Date: Sun, 10 Apr 2022 23:38:26 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH RFC v1 00/10] archs/random: fallback to using sched_clock() if no cycle counter To: Thomas Gleixner Cc: LKML , Linux Crypto Mailing List , Arnd Bergmann , "Theodore Ts'o" , Dominik Brodowski , Russell King , Catalin Marinas , Will Deacon , Geert Uytterhoeven , Thomas Bogendoerfer , Paul Walmsley , Palmer Dabbelt , Albert Ou , "David S . Miller" , Richard Weinberger , Anton Ivanov , Johannes Berg , Ingo Molnar , Borislav Petkov , Dave Hansen , "H . Peter Anvin" , Chris Zankel , Max Filippov , John Stultz , Stephen Boyd , linux-arm-kernel , linux-m68k , "open list:BROADCOM NVRAM DRIVER" , linux-riscv , sparclinux@vger.kernel.org, linux-um@lists.infradead.org, X86 ML , linux-xtensa@linux-xtensa.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi Thomas, On Sun, Apr 10, 2022 at 10:57 PM Thomas Gleixner wrote: > > Not yet having too much knowledge, I'm tentatively leaning toward the > > safe side, of just using ktime_read_raw_clock() in the current places > > that return zero all the time -- that is, for the purpose this patchset > > has. > > That's probably a good approach and it's init/runtime discoverable. Alright then. I'll send out a v2 and we'll see how that looks. Jason