f7f510ec19
Note that by itself, having a "hardware" random generator does very little: you should probably run "rngd" in your guest to feed this into the kernel entropy pool. Included: virtio_rng: dont use vmalloced addresses for virtio 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@de.ibm.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
14 lines
484 B
Makefile
14 lines
484 B
Makefile
#
|
|
# Makefile for HW Random Number Generator (RNG) device drivers.
|
|
#
|
|
|
|
obj-$(CONFIG_HW_RANDOM) += rng-core.o
|
|
rng-core-y := core.o
|
|
obj-$(CONFIG_HW_RANDOM_INTEL) += intel-rng.o
|
|
obj-$(CONFIG_HW_RANDOM_AMD) += amd-rng.o
|
|
obj-$(CONFIG_HW_RANDOM_GEODE) += geode-rng.o
|
|
obj-$(CONFIG_HW_RANDOM_VIA) += via-rng.o
|
|
obj-$(CONFIG_HW_RANDOM_IXP4XX) += ixp4xx-rng.o
|
|
obj-$(CONFIG_HW_RANDOM_OMAP) += omap-rng.o
|
|
obj-$(CONFIG_HW_RANDOM_PASEMI) += pasemi-rng.o
|
|
obj-$(CONFIG_HW_RANDOM_VIRTIO) += virtio-rng.o
|