linux-stable.git/tools/virtio/linux, branch linux-4.5.y

tools/virtio: use virt_xxx barriers

2016-01-26T08:18:29+00:00

Fix build after API changes.

Reported-by: Kamal Mostafa 
Signed-off-by: Michael S. Tsirkin

tools/virtio: fix byteswap logic

2015-12-07T15:28:10+00:00

commit cf561f0d2eb74574ad9985a2feab134267a9d298 ("virtio: introduce
virtio_is_little_endian() helper") changed byteswap logic to
skip feature bit checks for LE platforms, but didn't
update tools/virtio, so vring_bench started failing.

Update the copy under tools/virtio/ (TODO: find a way to avoid this code
duplication).

Cc: Greg Kurz 
Signed-off-by: Michael S. Tsirkin

tools/virtio: move list macro stubs

2015-12-07T15:28:09+00:00

Makes them more generally available.

Signed-off-by: Michael S. Tsirkin

tools/virtio: fix build after 4.2 changes

2015-09-09T19:03:30+00:00

more stubs, mostly

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: add support for 64 bit features.

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

Change u32 to u64, and use BIT_ULL and 1ULL everywhere.

Note: transports are unchanged, and only set low 32 bit.
This guarantees that no transport sets e.g. VERSION_1
by mistake without proper support.

Based on patch by Rusty.

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

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: Consolidate types.h

2014-05-01T19:22:39+00:00

Combine all definitions into a common tools/include/linux/types.h and
kill the wild growth elsewhere. Move DECLARE_BITMAP to its proper
bitmap.h header.

Signed-off-by: Borislav Petkov 
Acked-by: Rusty Russell 
Link: http://lkml.kernel.org/n/tip-azczs7qcv6h9xek9od10hiv2@git.kernel.org
Signed-off-by: Jiri Olsa

tools: Unify export.h

2014-05-01T19:18:17+00:00

So tools/ has been growing three, at a different stage of their
development export.h headers and so we should unite into one. Add
tools/include/ to the include path of virtio and liblockdep to pick the
shared header now.

Signed-off-by: Borislav Petkov 
Acked-by: Rusty Russell 
Cc: Arnaldo Carvalho de Melo 
Cc: Ingo Molnar 
Cc: Michael S. Tsirkin 
Cc: Paul Mackerras 
Cc: Peter Zijlstra 
Cc: Sasha Levin 
Cc: virtio-dev@lists.oasis-open.org
Cc: virtualization@lists.linux-foundation.org
Link: http://lkml.kernel.org/r/1397493185-19521-2-git-send-email-bp@alien8.de
Signed-off-by: Jiri Olsa

tools/virtio: fix missing kmemleak_ignore symbol

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

In commit bb478d8b167 virtio_ring: plug kmemleak false positive,
kmemleak_ignore was introduced. This broke compilation of virtio_test:

  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_ring.o ../../drivers/virtio/virtio_ring.c
  ../../drivers/virtio/virtio_ring.c: In function ‘vring_add_indirect’:
  ../../drivers/virtio/virtio_ring.c:177:2: warning: implicit declaration
  of function ‘kmemleak_ignore’ [-Wimplicit-function-declaration]
    kmemleak_ignore(desc);
    ^
  cc   virtio_test.o virtio_ring.o   -o virtio_test
  virtio_ring.o: In function `vring_add_indirect':
  tools/virtio/../../drivers/virtio/virtio_ring.c:177:
  undefined reference to `kmemleak_ignore'

Add a dummy header for tools/virtio, and add #incldue 
to drivers/virtio/virtio_ring.c so it is picked up by the userspace
tools.

Signed-off-by: Joel Stanley 
Signed-off-by: Rusty Russell