From: Gerd Hoffmann <kraxel@redhat.com>
To: Andy King <acking@vmware.com>
Cc: pv-drivers@vmware.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
gregkh@linuxfoundation.org, davem@davemloft.net
Subject: Re: [PATCH 0/1] VM Sockets for Linux upstreaming
Date: Tue, 05 Feb 2013 17:41:27 +0100 [thread overview]
Message-ID: <51113637.7070209@redhat.com> (raw)
In-Reply-To: <1360020362-25561-1-git-send-email-acking@vmware.com>
Hi,
> Unlike previous submissions, where the new socket family was entirely reliant
> on VMware's VMCI PCI device (and thus VMware's hypervisor), VM Sockets is now
> *completely* separated out into two parts, each in its own module:
Some separation still needs to be done:
CC [M] net/vmw_vsock/af_vsock.o
In file included from
/home/kraxel/projects/linux/net/vmw_vsock/af_vsock.c:102:0:
/home/kraxel/projects/linux/net/vmw_vsock/af_vsock.h:21:33: fatal error:
linux/vmw_vmci_defs.h: No such file or directory
compilation terminated.
make[4]: *** [net/vmw_vsock/af_vsock.o] Error 1
[ with vmci series from jan 9th applied on top it builds ]
Module deps are a bit bogous too:
vmw_vsock_vmci_transport 26162 0
vsock 34481 1 vmw_vsock_vmci_transport
vmw_vmci 61602 2 vsock,vmw_vsock_vmci_transport
Only vmw_vsock_vmci_transport should have a vmw_vmci dependency, not
vsock ...
Nevertheless this should be good enough to start hacking up a virtio
prototype.
cheers,
Gerd
next prev parent reply other threads:[~2013-02-05 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 23:26 [PATCH 0/1] VM Sockets for Linux upstreaming Andy King
2013-02-04 23:26 ` [PATCH 1/1] VSOCK: Introduce VM Sockets Andy King
2013-02-05 16:41 ` Gerd Hoffmann [this message]
2013-02-05 17:02 ` [PATCH 0/1] VM Sockets for Linux upstreaming Andy King
2013-02-07 0:32 ` [Pv-drivers] " Andy King
-- strict thread matches above, loose matches on Subject: below --
2013-02-07 0:23 Andy King
2013-02-11 1:10 ` David Miller
2013-01-25 17:37 acking
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=51113637.7070209@redhat.com \
--to=kraxel@redhat.com \
--cc=acking@vmware.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--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).