From: Amit Shah <amit.shah@redhat.com>
To: jgarzik@bitpay.com
Cc: hpa@linux.intel.com,
Virtualization List <virtualization@lists.linux-foundation.org>,
Amos Kong <akong@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, Amit Shah <amit.shah@redhat.com>
Subject: [PATCH 0/2] rng-tools: add udev rule for virtio-rng
Date: Thu, 7 Aug 2014 18:38:58 +0530 [thread overview]
Message-ID: <cover.1407416628.git.amit.shah@redhat.com> (raw)
Hello,
I didn't find a mailing list for rng-tools, so CC'ing the kernel lists
and the last few committers.
The first patch in this series adds a udev rule to start rngd for
guests that have a virtio-rng device available.
The second patch attempts to add autoconf magic to install the udev
rule in the system dirs. However, installing as non-root will
obviously fail. Prefixes are also not honoured. I don't know of a
better way, and we probably should leave this to distributions.
However, if someone has a better idea on how to expand this, please
suggest.
Amit Shah (2):
rngd: add udev rule to source from hwrng if virtio-rng present
Install udev rules in system-default directory
90-virtio-rng.rules | 1 +
Makefile.am | 1 +
configure.ac | 8 ++++++++
3 files changed, 10 insertions(+)
create mode 100644 90-virtio-rng.rules
--
1.9.3
next reply other threads:[~2014-08-07 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 13:08 Amit Shah [this message]
2014-08-07 13:08 ` [PATCH 1/2] rngd: add udev rule to source from hwrng if virtio-rng present Amit Shah
2014-08-07 19:31 ` H. Peter Anvin
2014-08-08 9:07 ` Amit Shah
2014-08-08 21:46 ` H. Peter Anvin
2014-08-11 7:15 ` Amit Shah
2014-08-11 13:30 ` Torsten Duwe
2014-08-11 16:50 ` H. Peter Anvin
2014-08-07 13:09 ` [PATCH 2/2] Install udev rules in system-default directory Amit Shah
[not found] ` <3df55388b1b3acd142f391494f102c3ddb2270ed.1407416628.git.amit.shah__45224.3810439997$1407417016$gmane$org@redhat.com>
2014-08-19 17:20 ` Paolo Bonzini
2014-08-20 4:36 ` Amit Shah
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=cover.1407416628.git.amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--cc=akong@redhat.com \
--cc=hpa@linux.intel.com \
--cc=jgarzik@bitpay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
/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).