- 23 9月, 2009 1 次提交
-
-
Virtio IDs are spread all over the tree which makes assigning new IDs bothersome. Putting them together should make the process less error-prone. Signed-off-by: NFernando Luis Vazquez Cao <fernando@oss.ntt.co.jp> Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
-
- 25 7月, 2008 1 次提交
-
-
由 Rusty Russell 提交于
We want others to implement and use virtio, so it makes sense to BSD license the non-__KERNEL__ parts of the headers to make this crystal clear. Signed-off-by: NRusty Russell <rusty@rustcorp.com.au> Acked-by: NChristian Borntraeger <borntraeger@de.ibm.com> Acked-by: NMark McLoughlin <markmc@redhat.com> Acked-by: NRyan Harper <ryanh@us.ibm.com> Acked-by: NEric Van Hensbergen <ericvh@gmail.com> Acked-by: NAnthony Liguori <aliguori@us.ibm.com>
-
- 30 5月, 2008 1 次提交
-
-
由 Rusty Russell 提交于
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: NChristian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
-