Hi Dave,
> >> Instead, what I remember doing was deferring to the feedback these
> >> folks received, stating that ideas that the virtio people had
> >> mentioned should be considered instead.
> >>
> >> http://marc.info/?l=linux-netdev&m=135301515818462&w=2
> >
> > I believe Andy replied to Anth
> > > Our position is that VSOCK feature set is more complete and that
> > > it
> > > should be possible to use transports other than VMCI for VSOCK
> > > traffic, should interested parties implement them,
> >
> > Implementing other transports requires restructing vsock (and vmci)
> > first as the
> > Our position is that VSOCK feature set is more complete and that it
> > should be possible to use transports other than VMCI for VSOCK
> > traffic, should interested parties implement them,
>
> Implementing other transports requires restructing vsock (and vmci)
> first as the current vsock cod
On 01/09/13 03:22, Dmitry Torokhov wrote:
> On Tue, Jan 08, 2013 at 05:46:01PM -0800, David Miller wrote:
>> I'd much rather see a hypervisor neutral solution than a hypervisor
>> specific one which this certainly is.
>
> Objectively speaking neither solution is hypervisor neutral as there are
> h
On Tue, Jan 08, 2013 at 05:46:01PM -0800, David Miller wrote:
> From: Dmitry Torokhov
> Date: Tue, 08 Jan 2013 17:41:44 -0800
>
> > On Tuesday, January 08, 2013 05:30:56 PM David Miller wrote:
> >> From: Greg KH
> >> Date: Tue, 8 Jan 2013 16:21:10 -0800
> >>
> >> > On Tue, Jan 08, 2013 at 03:59
From: Dmitry Torokhov
Date: Tue, 08 Jan 2013 17:41:44 -0800
> On Tuesday, January 08, 2013 05:30:56 PM David Miller wrote:
>> From: Greg KH
>> Date: Tue, 8 Jan 2013 16:21:10 -0800
>>
>> > On Tue, Jan 08, 2013 at 03:59:08PM -0800, George Zhang wrote:
>> >> * * *
>> >>
>> >> This series of VSOCK
On Tuesday, January 08, 2013 05:30:56 PM David Miller wrote:
> From: Greg KH
> Date: Tue, 8 Jan 2013 16:21:10 -0800
>
> > On Tue, Jan 08, 2013 at 03:59:08PM -0800, George Zhang wrote:
> >> * * *
> >>
> >> This series of VSOCK linux upstreaming patches include latest udpate from
> >> VMware to ad
From: Greg KH
Date: Tue, 8 Jan 2013 16:21:10 -0800
> On Tue, Jan 08, 2013 at 03:59:08PM -0800, George Zhang wrote:
>>
>> * * *
>>
>> This series of VSOCK linux upstreaming patches include latest udpate from
>> VMware to address Greg's and all other's code review comments.
>
> Dave, you acked t
On Tue, Jan 08, 2013 at 03:59:08PM -0800, George Zhang wrote:
>
> * * *
>
> This series of VSOCK linux upstreaming patches include latest udpate from
> VMware to address Greg's and all other's code review comments.
Dave, you acked these patches a while ago, and now that I've taken the
VMCI patch
* * *
This series of VSOCK linux upstreaming patches include latest udpate from
VMware to address Greg's and all other's code review comments.
Summary of changes:
- Rebase our linux kernel tree from v3.5 to v3.7.
- Fix all checkpatch warnings and errors. Fix some checkpatch with
Hi Anthony,
> This was already done in a hypervisor neutral way using virtio:
>
> http://lists.openwall.net/netdev/2008/12/14/8
>
> The concept was Nacked and that led to the abomination of
> virtio-serial. If an address family for virtualization is on the
> table, we should reconsider AF_VMCHA
* * *
This series of VSOCK linux upstreaming patches include latest udpate from
VMware.
Summary of changes:
- Sparse clean.
- Checkpatch clean with one exception, a "complex macro" in
which we can't add parentheses.
- Remove all runtime assertions.
- Fix
On Thu, 2012-11-15 at 15:32 -0600, Anthony Liguori wrote:
>
> The concept was Nacked and that led to the abomination of virtio-serial. If
> an
> address family for virtualization is on the table, we should reconsider
> AF_VMCHANNEL.
>
> I'd be thrilled to get rid of virtio-serial...
Ack.
Be
On 11/07/2012 12:58 AM, Gerd Hoffmann wrote:
On 11/05/12 19:19, Andy King wrote:
Hi David,
The big and only question is whether anyone can actually use any of
this stuff without your proprietary bits?
Do you mean the VMCI calls? The VMCI driver is in the process of being
upstreamed into the
Hi Sasha,
Thanks for taking a look.
> So all the documentation I see in the VMCI Socket Programming Guide
> is about userspace programming, and the documentation in af_vsock.c
> is all around implementation considerations.
Agreed, we're sorely lacking in proper documentation for the internal
pro
On 11/05/2012 01:32 PM, George Zhang wrote:
> Sasha,
> There is a 'brief' implementation notes aboutVSOCK protocol family
> in af_vsock.c. More about user space layer socket programming is from
> VMCI Socket Programming Guide. (remove crosst...@vmware.com for email
> bouncing).
> thanks,
> George
Hi Gerd,
>> Also, there was some interest from RedHat into using vSockets as
>> a unified interface, routed over a hypervisor-specific transport
>> (virtio or otherwise, although for now VMCI is the only one
>> implemented).
>
> Can you outline how this can be done? From a quick look over the
>
* * *
This series of VSOCK linux upstreaming patches include latest udpate from
VMware.
Summary of changes:
- Fix some new sparse issues.
- Remove some unneeded casts for VMCI.
- add more __user annotations for VMCI.
- Remove kernel version-specific bits from vSock
On 11/05/12 19:19, Andy King wrote:
> Hi David,
>
>> The big and only question is whether anyone can actually use any of
>> this stuff without your proprietary bits?
>
> Do you mean the VMCI calls? The VMCI driver is in the process of being
> upstreamed into the drivers/misc tree. Greg (cc'd on
Never mind, mail server seemed to be overloaded today.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Mon, 05 Nov 2012 10:00:38 -0800
George Zhang wrote:
> * * *
> This series of VSOCK linux upstreaming patches include latest udpate from
> VMware.
>
> Summary of changes:
> - Add include/linux/socket.h for AF_VSOCK.
> - Cleanup some comments.
> - Cleanup makefiles.
>
>
asha Levin"
To: "George Zhang"
Cc: net...@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualizat...@lists.linux-foundation.org, pv-driv...@vmware.com,
vm-crosst...@vmware.com, da...@davemloft.net, gre...@linuxfoundation.org
Sent: Monday, November 5, 2012 10:23:02 AM
Subject: R
g, pv-driv...@vmware.com,
vm-crosst...@vmware.com, gre...@linuxfoundation.org
Sent: Monday, November 5, 2012 10:10:37 AM
Subject: Re: [PATCH 0/6] VSOCK for Linux upstreaming
From: David Miller
Date: Mon, 05 Nov 2012 13:09:17 -0500 (EST)
> The big and only question is whether anyone can actually use any of
Hi George,
On Mon, Nov 5, 2012 at 1:00 PM, George Zhang wrote:
> For additional information about the use of VMCI and in particular
> VMCI Sockets, please refer to the VMCI Socket Programming Guide
> available at https://www.vmware.com/support/developer/vmci-sdk/.
Is there documentation about th
Hi David,
> The big and only question is whether anyone can actually use any of
> this stuff without your proprietary bits?
Do you mean the VMCI calls? The VMCI driver is in the process of being
upstreamed into the drivers/misc tree. Greg (cc'd on these patches) is
actively reviewing that code
From: David Miller
Date: Mon, 05 Nov 2012 13:09:17 -0500 (EST)
> The big and only question is whether anyone can actually use any of
> this stuff without your proprietary bits?
And BTW vm-crosst...@vmware.com bounces, take it out of the CC: list
on all future emails.
--
To unsubscribe from this
The big and only question is whether anyone can actually use any of
this stuff without your proprietary bits?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-in
* * *
This series of VSOCK linux upstreaming patches include latest udpate from
VMware.
Summary of changes:
- Add include/linux/socket.h for AF_VSOCK.
- Cleanup some comments.
- Cleanup makefiles.
* * *
In an effort to improve the out-of-the-box experience with Linux
ke
* * *
In an effort to improve the out-of-the-box experience with Linux
kernels for VMware users, VMware is working on readying the Virtual
Machine Communication Interface (vmw_vmci) and VMCI Sockets (VSOCK)
(vmw_vsock) kernel modules for inclusion in the Linux kernel. The
purpose of this post is
29 matches
Mail list logo
