From: Stefan Hajnoczi <stefanha@redhat.com>
To: kvm@vger.kernel.org
Cc: Matt Benjamin <mbenjamin@redhat.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
matt.ma@linaro.org, virtualization@lists.linux-foundation.org,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [RFC v4 1/5] VSOCK: transport-specific vsock_transport functions
Date: Tue, 22 Dec 2015 17:07:34 +0800 [thread overview]
Message-ID: <1450775258-18287-2-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1450775258-18287-1-git-send-email-stefanha@redhat.com>
struct vsock_transport contains function pointers called by AF_VSOCK
core code. The transport may want its own transport-specific function
pointers and they can be added after struct vsock_transport.
Allow the transport to fetch vsock_transport. It can downcast it to
access transport-specific function pointers.
The virtio transport will use this.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
include/net/af_vsock.h | 3 +++
net/vmw_vsock/af_vsock.c | 9 +++++++++
2 files changed, 12 insertions(+)
diff --git a/include/net/af_vsock.h b/include/net/af_vsock.h
index e9eb2d6..23f5525 100644
--- a/include/net/af_vsock.h
+++ b/include/net/af_vsock.h
@@ -165,6 +165,9 @@ static inline int vsock_core_init(const struct vsock_transport *t)
}
void vsock_core_exit(void);
+/* The transport may downcast this to access transport-specific functions */
+const struct vsock_transport *vsock_core_get_transport(void);
+
/**** UTILS ****/
void vsock_release_pending(struct sock *pending);
diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
index 7fd1220..9783a38 100644
--- a/net/vmw_vsock/af_vsock.c
+++ b/net/vmw_vsock/af_vsock.c
@@ -1994,6 +1994,15 @@ void vsock_core_exit(void)
}
EXPORT_SYMBOL_GPL(vsock_core_exit);
+const struct vsock_transport *vsock_core_get_transport(void)
+{
+ /* vsock_register_mutex not taken since only the transport uses this
+ * function and only while registered.
+ */
+ return transport;
+}
+EXPORT_SYMBOL_GPL(vsock_core_get_transport);
+
MODULE_AUTHOR("VMware, Inc.");
MODULE_DESCRIPTION("VMware Virtual Socket Family");
MODULE_VERSION("1.0.1.0-k");
--
2.5.0
next prev parent reply other threads:[~2015-12-22 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 9:07 [RFC v4 0/5] Add virtio transport for AF_VSOCK Stefan Hajnoczi
2015-12-22 9:07 ` Stefan Hajnoczi [this message]
2015-12-22 9:07 ` [RFC v4 2/5] VSOCK: Introduce virtio_vsock_common.ko Stefan Hajnoczi
2015-12-22 9:07 ` [RFC v4 3/5] VSOCK: Introduce virtio_transport.ko Stefan Hajnoczi
2015-12-22 9:07 ` [RFC v4 4/5] VSOCK: Introduce vhost_vsock.ko Stefan Hajnoczi
2015-12-22 9:07 ` [RFC v4 5/5] VSOCK: Add Makefile and Kconfig Stefan Hajnoczi
2016-01-04 7:55 ` [RFC v4 0/5] Add virtio transport for AF_VSOCK Jason Wang
2016-01-07 8:34 ` Stefan Hajnoczi
2016-01-28 15:19 ` Stefan Hajnoczi
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=1450775258-18287-2-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=matt.ma@linaro.org \
--cc=mbenjamin@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).