From: Christoph Hellwig <hch@infradead.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
Stephan Mueller <smueller@chronox.de>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
Android Kernel Team <kernel-team@android.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] crypto: jitterentropy - bind statically into kernel
Date: Mon, 5 Oct 2020 07:56:44 +0100 [thread overview]
Message-ID: <20201005065644.GB7462@infradead.org> (raw)
In-Reply-To: <CAMj1kXFL4gfrK1+zRG9sajTk62yRh3WzBG46KfKD=iM=VQMTAQ@mail.gmail.com>
On Mon, Oct 05, 2020 at 08:44:39AM +0200, Ard Biesheuvel wrote:
> 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.
Indeed. No need for my earlier idea..
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2020-10-05 6:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 6:56 [PATCH] clocksource: clint: Export clint_time_val for modules Palmer Dabbelt
2020-10-02 6:49 ` get_cycles from modular code in jitterentropy, was " Christoph Hellwig
2020-10-02 6:55 ` Stephan Mueller
2020-10-04 18:48 ` [PATCH] crypto: jitterentropy - bind statically into kernel Stephan Müller
2020-10-04 21:16 ` Ard Biesheuvel
2020-10-04 22:05 ` Palmer Dabbelt
2020-10-05 6:19 ` Christoph Hellwig
2020-10-05 6:24 ` Ard Biesheuvel
2020-10-05 6:40 ` Stephan Mueller
2020-10-05 6:44 ` Christoph Hellwig
2020-10-05 6:44 ` Ard Biesheuvel
2020-10-05 6:56 ` Christoph Hellwig [this message]
2020-10-05 7:45 ` Stephan Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201005065644.GB7462@infradead.org \
--to=hch@infradead.org \
--cc=ardb@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=palmerdabbelt@google.com \
--cc=smueller@chronox.de \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).