linux.git/tools/virtio/virtio_test.c, branch v4.12

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

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

tools/virtio: add virtio 1.0 in virtio_test

2014-12-15T21:49:22+00:00

Signed-off-by: Michael S. Tsirkin

tools/virtio: more stubs

2014-12-15T21:49:19+00:00

As usual, add more stubs to fix test build after main
codebase changes.

Signed-off-by: Michael S. Tsirkin

virtio: use u32, not bitmap for features

2014-12-09T10:05:23+00:00

It seemed like a good idea to use bitmap for features
in struct virtio_device, but it's actually a pain,
and seems to become even more painful when we get more
than 32 feature bits.  Just change it to a u32 for now.

Based on patch by Rusty.

Suggested-by: David Hildenbrand 
Signed-off-by: Rusty Russell 
Signed-off-by: Cornelia Huck 
Signed-off-by: Michael S. Tsirkin 
Reviewed-by: Cornelia Huck

tools/virtio: add a missing )

2014-03-13T00:53:25+00:00

Fixes the following build failure:

 cc -g -O2 -Wall -I. -I ../../usr/include/ -Wno-pointer-sign
   -fno-strict-overflow -fno-strict-aliasing -fno-common -MMD
   -U_FORTIFY_SOURCE   -c -o virtio_test.o virtio_test.c
 virtio_test.c: In function ‘run_test’:
 virtio_test.c:176:7: error: expected ‘)’ before ‘r’
         r = -1;
         ^

Fixes: 53c18c9906441 (virtio_test: verify if virtqueue_kick() succeeded)
Cc: Heinz Graalfs 
Signed-off-by: Joel Stanley 
Acked-by: Michael S. Tsirkin 
Signed-off-by: Rusty Russell

virtio_test: verify if virtqueue_kick() succeeded

2013-10-29T00:58:16+00:00

Verify if a host kick succeeded by checking return value of virtqueue_kick().

Signed-off-by: Heinz Graalfs 
Signed-off-by: Rusty Russell

virtio_ring: change host notification API

2013-10-29T00:58:11+00:00

Currently a host kick error is silently ignored and not reflected in
the virtqueue of a particular virtio device.

Changing the notify API for guest->host notification seems to be one
prerequisite in order to be able to handle such errors in the context
where the kick is triggered.

This patch changes the notify API. The notify function must return a
bool return value. It returns false if the host notification failed.

Signed-off-by: Heinz Graalfs 
Signed-off-by: Rusty Russell

tools/virtio: remove virtqueue_add_buf() from tests.

2013-03-20T05:15:07+00:00

Make the rest of the paths use virtqueue_add_sgs or add_outbuf.

Signed-off-by: Rusty Russell

tools/virtio: separate headers more.

2013-03-20T03:30:42+00:00

This makes them a bit more like the kernel headers, so we can include more
real kernel headers in our tests.

In addition this means that we don't break tools/virtio with the next
patch.

Signed-off-by: Rusty Russell