lkml.org 
[lkml]   [2020]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [PATCH] crypto: jitterentropy - bind statically into kernel
    On Mon, 5 Oct 2020 at 08:40, Stephan Mueller <smueller@chronox.de> wrote:
    >
    > Am Montag, 5. Oktober 2020, 08:24:46 CEST schrieb Ard Biesheuvel:
    >
    > Hi Ard,
    >
    > > If jitterentropy is a special case, we could put a alternate
    > > non-'static inline' version of random_get_entropy() in the core
    > > kernel, and only export it if JITTER_ENTROPY is built as a module in
    > > the first place. But I'd prefer it if jitterentropy switches to an API
    > > that is suitable for driver consumption.
    >
    > Which API do you have in mind? In user space, I use
    > clock_gettime(CLOCK_REALTIME) which also considers the clock source.
    >

    AFAICT, that call is backed by ktime_get_real_ts64(), which is already
    being exported to modules.

    Could you please check whether that works for your driver?

    \
     
     \ /
      Last update: 2020-10-05 08:45    [W:6.158 / U:0.048 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site