search for: virtio_rng

If virtio_rng is build as a module, random_data is an address in vmalloc space. As virtio expects guest real addresses, this can cause any kind of funny behaviour, so lets allocate random_data dynamically with kmalloc. Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com> --- drivers/char/hw...

If virtio_rng is build as a module, random_data is an address in vmalloc space. As virtio expects guest real addresses, this can cause any kind of funny behaviour, so lets allocate random_data dynamically with kmalloc. Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com> --- drivers/char/hw...

Hello Rusty, The entropy device was added after we exported all virtio headers. This patch adds virtio_rng.h to the exportable userspace headers. Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com> --- include/linux/Kbuild | 1 + 1 file changed, 1 insertion(+) Index: linux-2.6/include/linux/Kbuild =================================================================== --- linux-2.6...

...: Rusty Russell <rusty@rustcorp.com.au> --- Documentation/lguest/lguest.c | 53 +++++++++++++++ drivers/char/hw_random/Kconfig | 10 +++ drivers/char/hw_random/Makefile | 1 + drivers/char/hw_random/virtio-rng.c | 124 +++++++++++++++++++++++++++++++++++ include/linux/virtio_rng.h | 8 ++ 5 files changed, 196 insertions(+), 0 deletions(-) create mode 100644 drivers/char/hw_random/virtio-rng.c create mode 100644 include/linux/virtio_rng.h diff --git a/Documentation/lguest/lguest.c b/Documentation/lguest/lguest.c index 029cc7c..314e977 100644 --- a/Documentati...

...: Rusty Russell <rusty@rustcorp.com.au> --- Documentation/lguest/lguest.c | 53 +++++++++++++++ drivers/char/hw_random/Kconfig | 10 +++ drivers/char/hw_random/Makefile | 1 + drivers/char/hw_random/virtio-rng.c | 124 +++++++++++++++++++++++++++++++++++ include/linux/virtio_rng.h | 8 ++ 5 files changed, 196 insertions(+), 0 deletions(-) create mode 100644 drivers/char/hw_random/virtio-rng.c create mode 100644 include/linux/virtio_rng.h diff --git a/Documentation/lguest/lguest.c b/Documentation/lguest/lguest.c index 029cc7c..314e977 100644 --- a/Documentati...

...drivers/s390/kvm/kvm_virtio.c | 18 ++--- drivers/virtio/virtio.c | 8 ++- drivers/virtio/virtio_pci.c | 7 -- drivers/virtio/virtio_ring.c | 8 -- include/linux/virtio_blk.h | 9 +- include/linux/virtio_config.h | 6 +- include/linux/virtio_rng.h | 8 ++ 14 files changed, 225 insertions(+), 53 deletions(-) create mode 100644 drivers/char/hw_random/virtio-rng.c create mode 100644 include/linux/virtio_rng.h

Rusty, This patch changes the virtio_rng to a callback without a return value. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> --- drivers/char/hw_random/virtio-rng.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) Index: kvm/drivers/char/hw_random/virtio-rng.c ========================================...

Rusty, This patch changes the virtio_rng to a callback without a return value. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> --- drivers/char/hw_random/virtio-rng.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) Index: kvm/drivers/char/hw_random/virtio-rng.c ========================================...

...drivers/s390/kvm/kvm_virtio.c | 18 ++--- drivers/virtio/virtio.c | 8 ++- drivers/virtio/virtio_pci.c | 7 -- drivers/virtio/virtio_ring.c | 8 -- include/linux/virtio_blk.h | 9 +- include/linux/virtio_config.h | 6 +- include/linux/virtio_rng.h | 8 ++ 14 files changed, 225 insertions(+), 53 deletions(-) create mode 100644 drivers/char/hw_random/virtio-rng.c create mode 100644 include/linux/virtio_rng.h

Hi, I am virtualizing with KVM via libvirt and virt-manager. To have decent amounts of Entropy in the guest, I tried loading virtio_rng in a running VM. Despite the module being loaded, I didn't get any log entries, and also no /dev/hwrng. Do I need to enable the virtualized random generator in libvirt/virt-manager? If so, how do I do that? Is the support for this rather recent feature already implemented in qemu-kvm 1.0, libv...

...hwrng core supports to register multiple hwrng devices, and there is only one device really works in the same time. QEMU alsu supports to have multiple virtio-rng backends. This patch changes virtio-rng driver to support multiple virtio-rng devices. ]# cat /sys/class/misc/hw_random/rng_available virtio_rng.0 virtio_rng.1 ]# cat /sys/class/misc/hw_random/rng_current virtio_rng.0 ]# echo -n virtio_rng.1 > /sys/class/misc/hw_random/rng_current ]# dd if=/dev/hwrng of=/dev/null Signed-off-by: Amos Kong <akong at redhat.com> --- drivers/char/hw_random/virtio-rng.c | 102 ++++++++++++++++++++++---...

...hwrng core supports to register multiple hwrng devices, and there is only one device really works in the same time. QEMU alsu supports to have multiple virtio-rng backends. This patch changes virtio-rng driver to support multiple virtio-rng devices. ]# cat /sys/class/misc/hw_random/rng_available virtio_rng.0 virtio_rng.1 ]# cat /sys/class/misc/hw_random/rng_current virtio_rng.0 ]# echo -n virtio_rng.1 > /sys/class/misc/hw_random/rng_current ]# dd if=/dev/hwrng of=/dev/null Signed-off-by: Amos Kong <akong at redhat.com> --- drivers/char/hw_random/virtio-rng.c | 102 ++++++++++++++++++++++---...

..."virtio-net-pci" -#else /* ARMv7 */ +#ifdef __arm__ #define VIRTIO_BLK "virtio-blk-device" #define VIRTIO_SCSI "virtio-scsi-device" #define VIRTIO_SERIAL "virtio-serial-device" #define VIRTIO_NET "virtio-net-device" -#endif /* ARMv7 */ +#define VIRTIO_RNG "virtio-rng-device" +#endif + +#ifdef __s390x__ +#define VIRTIO_BLK "virtio-blk-ccw" +#define VIRTIO_SCSI "virtio-scsi-ccw" +#define VIRTIO_SERIAL "virtio-serial-ccw" +#define VIRTIO_NET "virtio-net-ccw" +#define VIRTIO_RNG "virtio-rng-ccw&quot...

Thanks: Cole Robinson, Dan Horak, Thomas Huth. --- lib/launch-libvirt.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/lib/launch-libvirt.c b/lib/launch-libvirt.c index f66c8e0ef..4adb2cfb3 100644 --- a/lib/launch-libvirt.c +++ b/lib/launch-libvirt.c @@ -1359,6 +1359,7 @@ construct_libvirt_xml_devices (guestfs_h *g, return -1; } +#ifndef __s390x__ /*

...ssell <rusty at rustcorp.com.au> > > There's currently a big lock around everything, and it means that we > can't query sysfs (eg /sys/devices/virtual/misc/hw_random/rng_current) > while the rng is reading. This is a real problem when the rng is slow, > or blocked (eg. virtio_rng with qemu's default /dev/random backend) > > This doesn't help (it leaves the current lock untouched), just adds a > lock to protect the read function and the static buffers, in preparation > for transition. > > Signed-off-by: Rusty Russell <rusty at rustcorp.com.au>...

...ssell <rusty at rustcorp.com.au> > > There's currently a big lock around everything, and it means that we > can't query sysfs (eg /sys/devices/virtual/misc/hw_random/rng_current) > while the rng is reading. This is a real problem when the rng is slow, > or blocked (eg. virtio_rng with qemu's default /dev/random backend) > > This doesn't help (it leaves the current lock untouched), just adds a > lock to protect the read function and the static buffers, in preparation > for transition. > > Signed-off-by: Rusty Russell <rusty at rustcorp.com.au>...

...need to > expose some API so that other kernel subsystems can request directly > notifications from the device. > > Signed-off-by: Babis Chalios <bchalios at amazon.es> > --- > drivers/char/hw_random/virtio-rng.c | 200 +++++++++++++++++++++++++++- > include/uapi/linux/virtio_rng.h | 3 + > 2 files changed, 197 insertions(+), 6 deletions(-) > > diff --git a/drivers/char/hw_random/virtio-rng.c b/drivers/char/hw_random/virtio-rng.c > index a6f3a8a2aca6..389a091a8801 100644 > --- a/drivers/char/hw_random/virtio-rng.c > +++ b/drivers/char/hw_random/virt...

...gt; > > > There's currently a big lock around everything, and it means that we > > > can't query sysfs (eg /sys/devices/virtual/misc/hw_random/rng_current) > > > while the rng is reading. This is a real problem when the rng is slow, > > > or blocked (eg. virtio_rng with qemu's default /dev/random backend) > > > > > > This doesn't help (it leaves the current lock untouched), just adds a > > > lock to protect the read function and the static buffers, in preparation > > > for transition. > > > > > > S...

...gt; > > > There's currently a big lock around everything, and it means that we > > > can't query sysfs (eg /sys/devices/virtual/misc/hw_random/rng_current) > > > while the rng is reading. This is a real problem when the rng is slow, > > > or blocked (eg. virtio_rng with qemu's default /dev/random backend) > > > > > > This doesn't help (it leaves the current lock untouched), just adds a > > > lock to protect the read function and the static buffers, in preparation > > > for transition. > > > > > > S...

...rp.com.au> > > > > There's currently a big lock around everything, and it means that we > > can't query sysfs (eg /sys/devices/virtual/misc/hw_random/rng_current) > > while the rng is reading. This is a real problem when the rng is slow, > > or blocked (eg. virtio_rng with qemu's default /dev/random backend) > > > > This doesn't help (it leaves the current lock untouched), just adds a > > lock to protect the read function and the static buffers, in preparation > > for transition. > > > > Signed-off-by: Rusty Russell &l...