From: Stefan Hajnoczi <stefanha@redhat.com>
To: netdev@vger.kernel.org
Cc: Jorgen Hansen <jhansen@vmware.com>,
Dexuan Cui <decui@microsoft.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH 0/5] VSOCK: add vsock_test test suite
Date: Wed, 13 Dec 2017 14:49:06 +0000 [thread overview]
Message-ID: <20171213144911.6428-1-stefanha@redhat.com> (raw)
The vsock_diag.ko module already has a test suite but the core AF_VSOCK
functionality has no tests. This patch series adds several test cases that
exercise AF_VSOCK SOCK_STREAM socket semantics (send/recv, connect/accept,
half-closed connections, simultaneous connections).
The test suite is modest but I hope to cover additional cases in the future.
My goal is to have a shared test suite so VMCI, Hyper-V, and KVM can ensure
that our transports behave the same.
I have tested virtio-vsock.
Jorgen: Please test the VMCI transport and let me know if anything needs to be
adjusted. See tools/testing/vsock/README for information on how to run the
test suite.
Dexuan: I'm not sure if this test suite is useful for the Hyper-V transport
since the host is Windows and uses a different API for AF_HYPERV?
Stefan Hajnoczi (5):
VSOCK: extract utility functions from vsock_diag_test.c
VSOCK: extract connect/accept functions from vsock_diag_test.c
VSOCK: add full barrier between test cases
VSOCK: add send_byte()/recv_byte() test utilities
VSOCK: add AF_VSOCK test cases
tools/testing/vsock/Makefile | 7 +-
tools/testing/vsock/util.h | 43 +++++
tools/testing/vsock/util.c | 291 ++++++++++++++++++++++++++++++
tools/testing/vsock/vsock_diag_test.c | 167 +++---------------
tools/testing/vsock/vsock_test.c | 321 ++++++++++++++++++++++++++++++++++
tools/testing/vsock/.gitignore | 1 +
tools/testing/vsock/README | 1 +
7 files changed, 685 insertions(+), 146 deletions(-)
create mode 100644 tools/testing/vsock/util.h
create mode 100644 tools/testing/vsock/util.c
create mode 100644 tools/testing/vsock/vsock_test.c
--
2.14.3
next reply other threads:[~2017-12-13 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 14:49 Stefan Hajnoczi [this message]
2017-12-13 14:49 ` [PATCH 1/5] VSOCK: extract utility functions from vsock_diag_test.c Stefan Hajnoczi
2017-12-13 14:49 ` [PATCH 2/5] VSOCK: extract connect/accept " Stefan Hajnoczi
2017-12-13 21:32 ` David Miller
2017-12-14 9:49 ` Stefan Hajnoczi
2017-12-13 14:49 ` [PATCH 3/5] VSOCK: add full barrier between test cases Stefan Hajnoczi
2017-12-13 14:49 ` [PATCH 4/5] VSOCK: add send_byte()/recv_byte() test utilities Stefan Hajnoczi
2017-12-13 14:49 ` [PATCH 5/5] VSOCK: add AF_VSOCK test cases Stefan Hajnoczi
2017-12-20 14:48 ` [PATCH 0/5] VSOCK: add vsock_test test suite Jorgen S. Hansen
2018-01-02 12:05 ` Stefan Hajnoczi
2018-01-03 16:09 ` Jorgen S. Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171213144911.6428-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=decui@microsoft.com \
--cc=jhansen@vmware.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox