16 Dec, 2016
1 commit
-
Despite living under drivers/ vringh.c is also used as part of the userspace
virtio tools. Before we can kill off the ACCESS_ONCE()definition in the tools,
we must convert vringh.c to use {READ,WRITE}_ONCE().This patch does so, along with the required include of for
the relevant definitions. The userspace tools provide their own definitions in
their own .Signed-off-by: Mark Rutland
Cc: Jason Wang
Cc: Michael S. Tsirkin
Cc: kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Michael S. Tsirkin
Reviewed-by: Christian Borntraeger
Reviewed-by: Cornelia Huck
Reviewed-by: Jason Wang
16 Dec, 2014
2 commits
-
When switching everything over to virtio 1.0 memory access APIs,
I missed converting vringh.
Fortunately, it's straight-forward.Signed-off-by: Michael S. Tsirkin
-
Pass u64 everywhere.
Signed-off-by: Michael S. Tsirkin
08 May, 2013
1 commit
-
[ 624.286653] vringh: module license 'unspecified' taints kernel.
Signed-off-by: Dave Jones
Signed-off-by: Rusty Russell
20 Mar, 2013
1 commit
-
Getting use of virtio rings correct is tricky, and a recent patch saw
an implementation of in-kernel rings (as separate from userspace).This abstracts the business of dealing with the virtio ring layout
from the access (userspace or direct); to do this, we use function
pointers, which gcc inlines correctly.Signed-off-by: Rusty Russell
Acked-by: Michael S. Tsirkin
