linux-toradex.git/tools/virtio, branch v4.12-rc4

tools/virtio: fix spelling mistake: "wakeus" -> "wakeups"

2017-05-09T13:43:24+00:00

trivial fix to spelling mistake in an error message.

Signed-off-by: Colin Ian King 
Signed-off-by: Michael S. Tsirkin 
Acked-by: Jason Wang

ptr_ring: support testing different batching sizes

2017-05-09T13:43:23+00:00

Use the param flag for that.

Signed-off-by: Michael S. Tsirkin

ringtest: support test specific parameters

2017-05-09T13:43:23+00:00

Add a new flag for passing test-specific parameters.

Signed-off-by: Michael S. Tsirkin

tools/virtio: fix build breakage

2017-05-02T20:41:43+00:00

Previous commit ("virtio: add context flag to find vqs")
added a new 'context' flag to vring_new_virtqueue(), but the
corresponding API in tools/virtio/ is not updated causing
build errors due to conflicting declarations.

Bring code in tools/virtio in sync with that in kernel.

I have used 'false' for the value of the new boolean 'context'
flag as that seems to be the best way to preserve existing
behavior.

Tested with:

$ make -C tools/virtio clean all ARCH=x86

Signed-off-by: Sekhar Nori 
Signed-off-by: Michael S. Tsirkin

ringtest: fix an assert statement

2017-05-02T20:41:42+00:00

There is an || vs && typo so the assert can never be triggered.

Signed-off-by: Dan Carpenter 
Signed-off-by: Michael S. Tsirkin 
Acked-by: Jason Wang

tools/virtio/ringtest: tweaks for s390

2017-01-19T21:46:32+00:00

Make ringtest work on s390 too.

Signed-off-by: Halil Pasic 
Acked-by: Sascha Silbe 
Signed-off-by: Cornelia Huck

tools/virtio/ringtest: fix run-on-all.sh for offline cpus

2017-01-19T21:46:31+00:00

Since ef1b144d ("tools/virtio/ringtest: fix run-on-all.sh to work
without /dev/cpu") run-on-all.sh uses seq 0 $HOST_AFFINITY as the list
of ids of the CPUs to run the command on (assuming ids of online CPUs
are consecutive and start from 0), where $HOST_AFFINITY is the highest
CPU id in the system previously determined using lscpu.  This can fail
on systems with offline CPUs.

Instead let's use lscpu to determine the list of online CPUs.

Signed-off-by: Halil Pasic 
Fixes: ef1b144d ("tools/virtio/ringtest: fix run-on-all.sh to work without
/dev/cpu")
Reviewed-by: Sascha Silbe 
Signed-off-by: Cornelia Huck

tools/virtio: use {READ,WRITE}_ONCE() in uaccess.h

2016-12-15T22:13:37+00:00

As a step towards killing off ACCESS_ONCE, use {READ,WRITE}_ONCE() for the
virtio tools uaccess primitives, pulling these in from .

With this done, we can kill off the now-unused ACCESS_ONCE() definition.

Signed-off-by: Mark Rutland 
Cc: Jason Wang 
Cc: Michael S. Tsirkin 
Cc: linux-kernel@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Michael S. Tsirkin 
Reviewed-by: Cornelia Huck 
Reviewed-by: Jason Wang

tools/virtio: fix READ_ONCE()

2016-12-15T22:13:36+00:00

The virtio tools implementation of READ_ONCE() has a single parameter called
'var', but erroneously refers to 'val' for its cast, and thus won't work unless
there's a variable of the correct type that happens to be called 'var'.

Fix this with s/var/val/, making READ_ONCE() work as expected regardless.

Fixes: a7c490333df3cff5 ("tools/virtio: use virt_xxx barriers")
Signed-off-by: Mark Rutland 
Cc: Jason Wang 
Cc: Michael S. Tsirkin 
Cc: linux-kernel@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Michael S. Tsirkin 
Reviewed-by: Cornelia Huck 
Reviewed-by: Jason Wang

ringtest: poll for new buffers once before updating event index

2016-10-30T22:21:43+00:00

Updating the event index has a memory barrier and causes more work
on the other side to actually signal the event.  It is unnecessary
if a new buffer has already appeared on the ring, so poll once before
doing the update.

The effect of this on the 0.9 ring implementation is pretty much
invisible, but on the new-style ring it provides a consistent 3%
performance improvement.

Signed-off-by: Paolo Bonzini 
Signed-off-by: Michael S. Tsirkin