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. Thanks Stephan
