On Wed, Dec 20, 2017 at 4:06 AM, Michael S. Tsirkin wrote:
> On Tue, Dec 19, 2017 at 05:05:59PM +, Stefan Hajnoczi wrote:
>> On Tue, Dec 19, 2017 at 2:56 PM, Michael S. Tsirkin wrote:
>> >> * Please handle short reads/writes and EAGAIN with the UNIX domain
On Tue, Dec 19, 2017 at 05:05:59PM +, Stefan Hajnoczi wrote:
> On Tue, Dec 19, 2017 at 2:56 PM, Michael S. Tsirkin wrote:
> >> * Please handle short reads/writes and EAGAIN with the UNIX domain
> >> socket. Do
> >>not use read/write_all() functions because they hang
On Tue, Dec 19, 2017 at 2:56 PM, Michael S. Tsirkin wrote:
>> * Please handle short reads/writes and EAGAIN with the UNIX domain socket.
>> Do
>>not use read/write_all() functions because they hang QEMU until I/O
>>completes.
>
> I'm not sure I agree with this one.
> * Please handle short reads/writes and EAGAIN with the UNIX domain socket.
> Do
>not use read/write_all() functions because they hang QEMU until I/O
>completes.
I'm not sure I agree with this one. vhost-user uses this extensively
right now. It might be a worth-while goal to drop this
On Tue, Dec 05, 2017 at 11:33:09AM +0800, Wei Wang wrote:
> Vhost-pci is a point-to-point based inter-VM communication solution. This
> patch series implements the vhost-pci-net device setup and emulation. The
> device is implemented as a virtio device, and it is set up via the
> vhost-user
On Fri, Dec 15, 2017 at 06:33:14PM +0800, Wei Wang wrote:
> On 12/14/2017 11:06 PM, Stefan Hajnoczi wrote:
> > On Wed, Dec 13, 2017 at 10:59:10PM +0200, Michael S. Tsirkin wrote:
> > > > * VHOST_USER_SET_VRING_KICK
> > > >
> > > > Set up vring kick doorbell (unless bit 8 is set) before
On Fri, Dec 15, 2017 at 05:10:37PM +0800, Wei Wang wrote:
> On 12/15/2017 01:32 AM, Stefan Hajnoczi wrote:
> > On Thu, Dec 14, 2017 at 01:53:16PM +0800, Wei Wang wrote:
> > > On 12/13/2017 08:35 PM, Stefan Hajnoczi wrote:
> > > > On Wed, Dec 13, 2017 at 04:11:45PM +0800, Wei Wang wrote:
> > > >
>
On 12/14/2017 11:06 PM, Stefan Hajnoczi wrote:
On Wed, Dec 13, 2017 at 10:59:10PM +0200, Michael S. Tsirkin wrote:
* VHOST_USER_SET_VRING_KICK
Set up vring kick doorbell (unless bit 8 is set) before sending
VHOST_USER_SET_VRING_KICK to the guest.
But guest can't use it, now can it?
On 12/15/2017 01:32 AM, Stefan Hajnoczi wrote:
On Thu, Dec 14, 2017 at 01:53:16PM +0800, Wei Wang wrote:
On 12/13/2017 08:35 PM, Stefan Hajnoczi wrote:
On Wed, Dec 13, 2017 at 04:11:45PM +0800, Wei Wang wrote:
I think the current approach is fine for a prototype but is not suitable
for wider
On Thu, Dec 14, 2017 at 01:53:16PM +0800, Wei Wang wrote:
> 3rd one: I'm not able to solve this one, as discussed, there are too many
> differences and it's too complex. I prefer the direction of simply gating
> the vhost-user protocol and deliver to the guest what it should see (just
> what this
On Thu, Dec 14, 2017 at 01:53:16PM +0800, Wei Wang wrote:
> On 12/13/2017 08:35 PM, Stefan Hajnoczi wrote:
> > On Wed, Dec 13, 2017 at 04:11:45PM +0800, Wei Wang wrote:
> >
> > I think the current approach is fine for a prototype but is not suitable
> > for wider use by the community because it:
On Wed, Dec 13, 2017 at 10:59:10PM +0200, Michael S. Tsirkin wrote:
> > * VHOST_USER_SET_VRING_KICK
> >
> >Set up vring kick doorbell (unless bit 8 is set) before sending
> >VHOST_USER_SET_VRING_KICK to the guest.
>
> But guest can't use it, now can it?
>
> What guest needs is a
On 12/13/2017 08:35 PM, Stefan Hajnoczi wrote:
On Wed, Dec 13, 2017 at 04:11:45PM +0800, Wei Wang wrote:
I think the current approach is fine for a prototype but is not suitable
for wider use by the community because it:
1. Does not scale to multiple device types (net, scsi, blk, etc)
2. Does
Hi Stefan,
On 12/13/2017 09:08 PM, Stefan Hajnoczi wrote:
On Wed, Dec 13, 2017 at 3:01 PM, Michael S. Tsirkin wrote:
On Wed, Dec 13, 2017 at 12:35:21PM +, Stefan Hajnoczi wrote:
I'm not saying that DPDK should use libvhost-user. I'm saying that it's
easy to add vfio
> * VHOST_USER_SET_VRING_KICK
>
>Set up vring kick doorbell (unless bit 8 is set) before sending
>VHOST_USER_SET_VRING_KICK to the guest.
But guest can't use it, now can it?
What guest needs is a mapping to interrupts.
> * VHOST_USER_SET_VRING_CALL
>
>Set up the vring call
On Wed, Dec 13, 2017 at 3:01 PM, Michael S. Tsirkin wrote:
> On Wed, Dec 13, 2017 at 12:35:21PM +, Stefan Hajnoczi wrote:
>> I'm not saying that DPDK should use libvhost-user. I'm saying that it's
>> easy to add vfio vhost-pci support (for the PCI adapter I described) to
>>
On Wed, Dec 13, 2017 at 12:35:21PM +, Stefan Hajnoczi wrote:
> I'm not saying that DPDK should use libvhost-user. I'm saying that it's
> easy to add vfio vhost-pci support (for the PCI adapter I described) to
> DPDK. This patch series would require writing a completely new slave
> for
On Wed, Dec 13, 2017 at 04:11:45PM +0800, Wei Wang wrote:
> On 12/12/2017 06:14 PM, Stefan Hajnoczi wrote:
> > On Mon, Dec 11, 2017 at 01:53:40PM +, Wang, Wei W wrote:
> > > On Monday, December 11, 2017 7:12 PM, Stefan Hajnoczi wrote:
> > > > On Sat, Dec 09, 2017 at 04:23:17PM +, Wang, Wei
On 12/12/2017 06:14 PM, Stefan Hajnoczi wrote:
On Mon, Dec 11, 2017 at 01:53:40PM +, Wang, Wei W wrote:
On Monday, December 11, 2017 7:12 PM, Stefan Hajnoczi wrote:
On Sat, Dec 09, 2017 at 04:23:17PM +, Wang, Wei W wrote:
On Friday, December 8, 2017 4:34 PM, Stefan Hajnoczi wrote:
On
On Mon, Dec 11, 2017 at 01:53:40PM +, Wang, Wei W wrote:
> On Monday, December 11, 2017 7:12 PM, Stefan Hajnoczi wrote:
> > On Sat, Dec 09, 2017 at 04:23:17PM +, Wang, Wei W wrote:
> > > On Friday, December 8, 2017 4:34 PM, Stefan Hajnoczi wrote:
> > > > On Fri, Dec 8, 2017 at 6:43 AM, Wei
On Monday, December 11, 2017 7:12 PM, Stefan Hajnoczi wrote:
> On Sat, Dec 09, 2017 at 04:23:17PM +, Wang, Wei W wrote:
> > On Friday, December 8, 2017 4:34 PM, Stefan Hajnoczi wrote:
> > > On Fri, Dec 8, 2017 at 6:43 AM, Wei Wang
> wrote:
> > > > On 12/08/2017 07:54 AM,
On Sat, Dec 09, 2017 at 04:23:17PM +, Wang, Wei W wrote:
> On Friday, December 8, 2017 4:34 PM, Stefan Hajnoczi wrote:
> > On Fri, Dec 8, 2017 at 6:43 AM, Wei Wang wrote:
> > > On 12/08/2017 07:54 AM, Michael S. Tsirkin wrote:
> > >>
> > >> On Thu, Dec 07, 2017 at
On Friday, December 8, 2017 4:34 PM, Stefan Hajnoczi wrote:
> On Fri, Dec 8, 2017 at 6:43 AM, Wei Wang wrote:
> > On 12/08/2017 07:54 AM, Michael S. Tsirkin wrote:
> >>
> >> On Thu, Dec 07, 2017 at 06:28:19PM +, Stefan Hajnoczi wrote:
> >>>
> >>> On Thu, Dec 7, 2017 at
On Friday, December 8, 2017 10:28 PM, Michael S. Tsirkin wrote:
> On Fri, Dec 08, 2017 at 06:08:05AM +, Stefan Hajnoczi wrote:
> > On Thu, Dec 7, 2017 at 11:54 PM, Michael S. Tsirkin
> wrote:
> > > On Thu, Dec 07, 2017 at 06:28:19PM +, Stefan Hajnoczi wrote:
> > >> On
On Fri, Dec 8, 2017 at 2:27 PM, Michael S. Tsirkin wrote:
> On Fri, Dec 08, 2017 at 06:08:05AM +, Stefan Hajnoczi wrote:
>> On Thu, Dec 7, 2017 at 11:54 PM, Michael S. Tsirkin wrote:
>> > On Thu, Dec 07, 2017 at 06:28:19PM +, Stefan Hajnoczi wrote:
>> >>
On Fri, Dec 08, 2017 at 06:08:05AM +, Stefan Hajnoczi wrote:
> On Thu, Dec 7, 2017 at 11:54 PM, Michael S. Tsirkin wrote:
> > On Thu, Dec 07, 2017 at 06:28:19PM +, Stefan Hajnoczi wrote:
> >> On Thu, Dec 7, 2017 at 5:38 PM, Michael S. Tsirkin wrote:
> >>
On Fri, Dec 8, 2017 at 6:43 AM, Wei Wang wrote:
> On 12/08/2017 07:54 AM, Michael S. Tsirkin wrote:
>>
>> On Thu, Dec 07, 2017 at 06:28:19PM +, Stefan Hajnoczi wrote:
>>>
>>> On Thu, Dec 7, 2017 at 5:38 PM, Michael S. Tsirkin
>>> wrote:
On
On 12/08/2017 07:54 AM, Michael S. Tsirkin wrote:
On Thu, Dec 07, 2017 at 06:28:19PM +, Stefan Hajnoczi wrote:
On Thu, Dec 7, 2017 at 5:38 PM, Michael S. Tsirkin wrote:
On Thu, Dec 07, 2017 at 05:29:14PM +, Stefan Hajnoczi wrote:
On Thu, Dec 7, 2017 at 4:47 PM,
On Thu, Dec 7, 2017 at 11:54 PM, Michael S. Tsirkin wrote:
> On Thu, Dec 07, 2017 at 06:28:19PM +, Stefan Hajnoczi wrote:
>> On Thu, Dec 7, 2017 at 5:38 PM, Michael S. Tsirkin wrote:
>> > On Thu, Dec 07, 2017 at 05:29:14PM +, Stefan Hajnoczi wrote:
>> >>
On Thu, Dec 07, 2017 at 06:28:19PM +, Stefan Hajnoczi wrote:
> On Thu, Dec 7, 2017 at 5:38 PM, Michael S. Tsirkin wrote:
> > On Thu, Dec 07, 2017 at 05:29:14PM +, Stefan Hajnoczi wrote:
> >> On Thu, Dec 7, 2017 at 4:47 PM, Michael S. Tsirkin wrote:
> >>
On Thu, Dec 7, 2017 at 5:38 PM, Michael S. Tsirkin wrote:
> On Thu, Dec 07, 2017 at 05:29:14PM +, Stefan Hajnoczi wrote:
>> On Thu, Dec 7, 2017 at 4:47 PM, Michael S. Tsirkin wrote:
>> > On Thu, Dec 07, 2017 at 04:29:45PM +, Stefan Hajnoczi wrote:
>> >>
On Thu, Dec 07, 2017 at 05:29:14PM +, Stefan Hajnoczi wrote:
> On Thu, Dec 7, 2017 at 4:47 PM, Michael S. Tsirkin wrote:
> > On Thu, Dec 07, 2017 at 04:29:45PM +, Stefan Hajnoczi wrote:
> >> On Thu, Dec 7, 2017 at 2:02 PM, Michael S. Tsirkin wrote:
> >>
On Thu, Dec 7, 2017 at 4:47 PM, Michael S. Tsirkin wrote:
> On Thu, Dec 07, 2017 at 04:29:45PM +, Stefan Hajnoczi wrote:
>> On Thu, Dec 7, 2017 at 2:02 PM, Michael S. Tsirkin wrote:
>> > On Thu, Dec 07, 2017 at 01:08:04PM +, Stefan Hajnoczi wrote:
>> >>
On Thu, Dec 07, 2017 at 04:29:45PM +, Stefan Hajnoczi wrote:
> On Thu, Dec 7, 2017 at 2:02 PM, Michael S. Tsirkin wrote:
> > On Thu, Dec 07, 2017 at 01:08:04PM +, Stefan Hajnoczi wrote:
> >> Instead of responding individually to these points, I hope this will
> >> explain
On Thu, Dec 7, 2017 at 2:02 PM, Michael S. Tsirkin wrote:
> On Thu, Dec 07, 2017 at 01:08:04PM +, Stefan Hajnoczi wrote:
>> Instead of responding individually to these points, I hope this will
>> explain my perspective. Let me know if you do want individual
>> responses, I'm
On Thu, Dec 07, 2017 at 01:08:04PM +, Stefan Hajnoczi wrote:
> Instead of responding individually to these points, I hope this will
> explain my perspective. Let me know if you do want individual
> responses, I'm happy to talk more about the points above but I think
> the biggest difference
On Thu, Dec 07, 2017 at 07:54:48AM +, Avi Cohen (A) wrote:
> There is already a virtio mechanism in which 2 VMs assigned a virtio device
> , are communicating via a veth pair in the host .
> KVM just passes a pointer of the page of the writer VM to the reader VM -
> resulting in
On Thu, Dec 7, 2017 at 9:02 AM, Wei Wang wrote:
> On 12/07/2017 02:31 PM, Stefan Hajnoczi wrote:
>>
>> On Thu, Dec 7, 2017 at 3:57 AM, Wei Wang wrote:
>>>
>>> On 12/07/2017 12:27 AM, Stefan Hajnoczi wrote:
On Wed, Dec 6, 2017 at 4:09 PM,
On 12/07/2017 02:31 PM, Stefan Hajnoczi wrote:
On Thu, Dec 7, 2017 at 3:57 AM, Wei Wang wrote:
On 12/07/2017 12:27 AM, Stefan Hajnoczi wrote:
On Wed, Dec 6, 2017 at 4:09 PM, Wang, Wei W wrote:
On Wednesday, December 6, 2017 9:50 PM, Stefan
On 2017年12月07日 16:04, Stefan Hajnoczi wrote:
On Thu, Dec 7, 2017 at 7:54 AM, Avi Cohen (A) wrote:
There is already a virtio mechanism in which 2 VMs assigned a virtio device ,
are communicating via a veth pair in the host .
KVM just passes a pointer of the page of
On Thu, Dec 7, 2017 at 7:54 AM, Avi Cohen (A) wrote:
> There is already a virtio mechanism in which 2 VMs assigned a virtio device
> , are communicating via a veth pair in the host .
> KVM just passes a pointer of the page of the writer VM to the reader VM -
> resulting
; Zhiyong; jan.kis...@siemens.com; jasow...@redhat.com; Avi Cohen (A);
> qemu-devel@nongnu.org; marcandre.lur...@redhat.com;
> pbonz...@redhat.com
> Subject: Re: [Qemu-devel] [virtio-dev] [PATCH v3 0/7] Vhost-pci for inter-VM
> communication
>
> On Thu, Dec 7, 2017 at 3:57 AM, W
On Thu, Dec 7, 2017 at 3:57 AM, Wei Wang wrote:
> On 12/07/2017 12:27 AM, Stefan Hajnoczi wrote:
>>
>> On Wed, Dec 6, 2017 at 4:09 PM, Wang, Wei W wrote:
>>>
>>> On Wednesday, December 6, 2017 9:50 PM, Stefan Hajnoczi wrote:
On Tue, Dec 05,
On 12/07/2017 01:11 PM, Michael S. Tsirkin wrote:
On Thu, Dec 07, 2017 at 11:57:33AM +0800, Wei Wang wrote:
On 12/07/2017 12:27 AM, Stefan Hajnoczi wrote:
On Wed, Dec 6, 2017 at 4:09 PM, Wang, Wei W wrote:
On Wednesday, December 6, 2017 9:50 PM, Stefan Hajnoczi wrote:
On Thu, Dec 07, 2017 at 11:57:33AM +0800, Wei Wang wrote:
> On 12/07/2017 12:27 AM, Stefan Hajnoczi wrote:
> > On Wed, Dec 6, 2017 at 4:09 PM, Wang, Wei W wrote:
> > > On Wednesday, December 6, 2017 9:50 PM, Stefan Hajnoczi wrote:
> > > > On Tue, Dec 05, 2017 at 11:33:09AM
On 12/07/2017 12:27 AM, Stefan Hajnoczi wrote:
On Wed, Dec 6, 2017 at 4:09 PM, Wang, Wei W wrote:
On Wednesday, December 6, 2017 9:50 PM, Stefan Hajnoczi wrote:
On Tue, Dec 05, 2017 at 11:33:09AM +0800, Wei Wang wrote:
Vhost-pci is a point-to-point based inter-VM
On Wed, Dec 6, 2017 at 4:09 PM, Wang, Wei W wrote:
> On Wednesday, December 6, 2017 9:50 PM, Stefan Hajnoczi wrote:
>> On Tue, Dec 05, 2017 at 11:33:09AM +0800, Wei Wang wrote:
>> > Vhost-pci is a point-to-point based inter-VM communication solution.
>> > This patch series
On Wed, Dec 6, 2017 at 1:49 PM, Stefan Hajnoczi wrote:
> On Tue, Dec 05, 2017 at 11:33:09AM +0800, Wei Wang wrote:
>> Vhost-pci is a point-to-point based inter-VM communication solution. This
>> patch series implements the vhost-pci-net device setup and emulation. The
>>
On Wednesday, December 6, 2017 9:50 PM, Stefan Hajnoczi wrote:
> On Tue, Dec 05, 2017 at 11:33:09AM +0800, Wei Wang wrote:
> > Vhost-pci is a point-to-point based inter-VM communication solution.
> > This patch series implements the vhost-pci-net device setup and
> > emulation. The device is
On Tue, Dec 05, 2017 at 11:33:09AM +0800, Wei Wang wrote:
> Vhost-pci is a point-to-point based inter-VM communication solution. This
> patch series implements the vhost-pci-net device setup and emulation. The
> device is implemented as a virtio device, and it is set up via the
> vhost-user
On Tue, Dec 05, 2017 at 11:33:09AM +0800, Wei Wang wrote:
> Vhost-pci is a point-to-point based inter-VM communication solution. This
> patch series implements the vhost-pci-net device setup and emulation. The
> device is implemented as a virtio device, and it is set up via the
> vhost-user
> -Original Message-
> From: Jason Wang [mailto:jasow...@redhat.com]
> Sent: Tuesday, 05 December, 2017 9:19 AM
> To: Wei Wang; virtio-...@lists.oasis-open.org; qemu-devel@nongnu.org;
> m...@redhat.com; marcandre.lur...@redhat.com; stefa...@redhat.com;
> pbonz...@redhat.com
> Cc:
On Tue, Dec 05, 2017 at 11:33:09AM +0800, Wei Wang wrote:
> Vhost-pci is a point-to-point based inter-VM communication solution. This
> patch series implements the vhost-pci-net device setup and emulation. The
> device is implemented as a virtio device, and it is set up via the
> vhost-user
On 12/05/2017 04:49 PM, Avi Cohen (A) wrote:
-Original Message-
From: Jason Wang [mailto:jasow...@redhat.com]
Sent: Tuesday, 05 December, 2017 9:19 AM
To: Wei Wang; virtio-...@lists.oasis-open.org; qemu-devel@nongnu.org;
m...@redhat.com; marcandre.lur...@redhat.com;
On 2017年12月05日 15:15, Wei Wang wrote:
On 12/05/2017 03:01 PM, Jason Wang wrote:
On 2017年12月05日 11:33, Wei Wang wrote:
Vhost-pci is a point-to-point based inter-VM communication solution.
This
patch series implements the vhost-pci-net device setup and
emulation. The
device is implemented
On 12/05/2017 03:01 PM, Jason Wang wrote:
On 2017年12月05日 11:33, Wei Wang wrote:
Vhost-pci is a point-to-point based inter-VM communication solution.
This
patch series implements the vhost-pci-net device setup and emulation.
The
device is implemented as a virtio device, and it is set up via
On 2017年12月05日 11:33, Wei Wang wrote:
Vhost-pci is a point-to-point based inter-VM communication solution. This
patch series implements the vhost-pci-net device setup and emulation. The
device is implemented as a virtio device, and it is set up via the
vhost-user protocol to get the neessary
57 matches
Mail list logo