From: Stephan Mueller <smueller@chronox.de>
To: herbert@gondor.apana.org.au, Theodore Tso <tytso@mit.edu>
Cc: sandyinchina@gmail.com, Jason Cooper <jason@lakedaemon.net>,
John Denker <jsd@av8n.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 5/6] crypto: LRNG - hook LRNG into interrupt handler
Date: Sun, 24 Apr 2016 12:42:57 +0200 [thread overview]
Message-ID: <1597982.NXJbFZcdAH@positron.chronox.de> (raw)
In-Reply-To: <1589319.WyasadRQQe@positron.chronox.de>
The LRNG places a callback into the interrupt handler to be triggered
for each interrupt. With this callback, entropy is collected.
Signed-off-by: Stephan Mueller <smueller@chronox.de>
---
kernel/irq/handle.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
index a15b548..8d64e37 100644
--- a/kernel/irq/handle.c
+++ b/kernel/irq/handle.c
@@ -175,6 +175,7 @@ irqreturn_t handle_irq_event_percpu(struct irq_desc *desc)
}
add_interrupt_randomness(irq, flags);
+ lrng_irq_process();
if (!noirqdebug)
note_interrupt(desc, retval);
--
2.5.5
next prev parent reply other threads:[~2016-04-24 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 10:38 [PATCH v2 0/6] /dev/random - a new approach Stephan Mueller
2016-04-24 10:39 ` [PATCH v2 1/6] crypto: DRBG - externalize DRBG functions for LRNG Stephan Mueller
2016-04-24 10:40 ` [PATCH v2 2/6] random: conditionally compile code depending on LRNG Stephan Mueller
2016-04-24 10:40 ` [PATCH v2 3/6] crypto: Linux Random Number Generator Stephan Mueller
2016-04-24 11:30 ` Joe Perches
2016-04-24 14:12 ` Stephan Mueller
2016-04-24 16:43 ` Joe Perches
2016-04-24 10:42 ` [PATCH v2 4/6] crypto: LRNG - enable compile Stephan Mueller
2016-04-24 10:42 ` Stephan Mueller [this message]
2016-04-24 10:44 ` [PATCH v2 6/6] hyperv IRQ handler: trigger LRNG 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=1597982.NXJbFZcdAH@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=jason@lakedaemon.net \
--cc=jsd@av8n.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandyinchina@gmail.com \
--cc=tytso@mit.edu \
/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
Powered by JetHome