On Tue, Feb 06, 2018 at 12:42:36PM +, Wang, Wei W wrote:
> On Tuesday, February 6, 2018 5:32 PM, Stefan Hajnoczi wrote:
> > On Tue, Feb 06, 2018 at 01:28:25AM +, Wang, Wei W wrote:
> > > On Tuesday, February 6, 2018 12:26 AM, Stefan Hajnoczi wrote:
> > > > On Fri, Feb 02, 2018 at 09:08:44PM
On Tuesday, February 6, 2018 5:32 PM, Stefan Hajnoczi wrote:
> On Tue, Feb 06, 2018 at 01:28:25AM +, Wang, Wei W wrote:
> > On Tuesday, February 6, 2018 12:26 AM, Stefan Hajnoczi wrote:
> > > On Fri, Feb 02, 2018 at 09:08:44PM +0800, Wei Wang wrote:
> > > > On 02/02/2018 01:08 AM, Michael S. Ts
On Tue, Feb 06, 2018 at 01:28:25AM +, Wang, Wei W wrote:
> On Tuesday, February 6, 2018 12:26 AM, Stefan Hajnoczi wrote:
> > On Fri, Feb 02, 2018 at 09:08:44PM +0800, Wei Wang wrote:
> > > On 02/02/2018 01:08 AM, Michael S. Tsirkin wrote:
> > > > On Tue, Jan 30, 2018 at 08:09:19PM +0800, Wei Wa
On Tuesday, February 6, 2018 12:26 AM, Stefan Hajnoczi wrote:
> On Fri, Feb 02, 2018 at 09:08:44PM +0800, Wei Wang wrote:
> > On 02/02/2018 01:08 AM, Michael S. Tsirkin wrote:
> > > On Tue, Jan 30, 2018 at 08:09:19PM +0800, Wei Wang wrote:
> > > > Issues:
> > > > Suppose we have both the vhost and
On Fri, Feb 02, 2018 at 09:08:44PM +0800, Wei Wang wrote:
> On 02/02/2018 01:08 AM, Michael S. Tsirkin wrote:
> > On Tue, Jan 30, 2018 at 08:09:19PM +0800, Wei Wang wrote:
> > > Issues:
> > > Suppose we have both the vhost and virtio-net set up, and vhost pmd <->
> > > virtio-net pmd communication
On Mon, Feb 05, 2018 at 09:57:23AM +, Wang, Wei W wrote:
> On Friday, February 2, 2018 11:26 PM, Stefan Hajnoczi wrote:
> > On Tue, Jan 30, 2018 at 08:09:19PM +0800, Wei Wang wrote:
> > > Background:
> > > The vhost-user negotiation is split into 2 phases currently. The 1st
> > > phase happens
On Friday, February 2, 2018 11:26 PM, Stefan Hajnoczi wrote:
> On Tue, Jan 30, 2018 at 08:09:19PM +0800, Wei Wang wrote:
> > Background:
> > The vhost-user negotiation is split into 2 phases currently. The 1st
> > phase happens when the connection is established, and we can find
> > what's done in
On Tue, Jan 30, 2018 at 08:09:19PM +0800, Wei Wang wrote:
> On 01/26/2018 10:44 PM, Stefan Hajnoczi wrote:
> > On Thu, Jan 25, 2018 at 06:19:13PM +0800, Wei Wang wrote:
> > > On 01/24/2018 07:40 PM, Stefan Hajnoczi wrote:
> > > > On Tue, Jan 23, 2018 at 09:06:49PM +0800, Wei Wang wrote:
> > > > > O
On 02/02/2018 01:08 AM, Michael S. Tsirkin wrote:
On Tue, Jan 30, 2018 at 08:09:19PM +0800, Wei Wang wrote:
Issues:
Suppose we have both the vhost and virtio-net set up, and vhost pmd <->
virtio-net pmd communication works well. Now, vhost pmd exits (virtio-net
pmd is still there). Some time lat
On Tue, Jan 30, 2018 at 08:09:19PM +0800, Wei Wang wrote:
> Issues:
> Suppose we have both the vhost and virtio-net set up, and vhost pmd <->
> virtio-net pmd communication works well. Now, vhost pmd exits (virtio-net
> pmd is still there). Some time later, we re-run vhost pmd, the vhost pmd
> does
On 01/26/2018 10:44 PM, Stefan Hajnoczi wrote:
On Thu, Jan 25, 2018 at 06:19:13PM +0800, Wei Wang wrote:
On 01/24/2018 07:40 PM, Stefan Hajnoczi wrote:
On Tue, Jan 23, 2018 at 09:06:49PM +0800, Wei Wang wrote:
On 01/23/2018 07:12 PM, Stefan Hajnoczi wrote:
On Mon, Jan 22, 2018 at 07:09:06PM +
On Thu, Jan 25, 2018 at 06:19:13PM +0800, Wei Wang wrote:
> On 01/24/2018 07:40 PM, Stefan Hajnoczi wrote:
> > On Tue, Jan 23, 2018 at 09:06:49PM +0800, Wei Wang wrote:
> > > On 01/23/2018 07:12 PM, Stefan Hajnoczi wrote:
> > > > On Mon, Jan 22, 2018 at 07:09:06PM +0800, Wei Wang wrote:
> > > > > O
On 2018年01月25日 22:48, Michael S. Tsirkin wrote:
On Thu, Jan 25, 2018 at 03:07:23PM +0100, Paolo Bonzini wrote:
On 23/01/2018 17:07, Michael S. Tsirkin wrote:
It's not clear to me how to do this. E.g need a way to report failure to VM2
or #PF?
Why would there be a failure? qemu running vm1 wo
On Thu, Jan 25, 2018 at 03:07:23PM +0100, Paolo Bonzini wrote:
> On 23/01/2018 17:07, Michael S. Tsirkin wrote:
> >> It's not clear to me how to do this. E.g need a way to report failure to
> >> VM2
> >> or #PF?
> >
> > Why would there be a failure? qemu running vm1 would be responsible for
> > p
On 23/01/2018 17:07, Michael S. Tsirkin wrote:
>> It's not clear to me how to do this. E.g need a way to report failure to VM2
>> or #PF?
>
> Why would there be a failure? qemu running vm1 would be responsible for
> preventing access to vm2's memory not mapped through an IOMMU.
> Basically munmap
On 01/24/2018 07:40 PM, Stefan Hajnoczi wrote:
On Tue, Jan 23, 2018 at 09:06:49PM +0800, Wei Wang wrote:
On 01/23/2018 07:12 PM, Stefan Hajnoczi wrote:
On Mon, Jan 22, 2018 at 07:09:06PM +0800, Wei Wang wrote:
On 01/19/2018 09:06 PM, Stefan Hajnoczi wrote:
- Suppose in the future there is
On Tue, Jan 23, 2018 at 09:06:49PM +0800, Wei Wang wrote:
> On 01/23/2018 07:12 PM, Stefan Hajnoczi wrote:
> > On Mon, Jan 22, 2018 at 07:09:06PM +0800, Wei Wang wrote:
> > > On 01/19/2018 09:06 PM, Stefan Hajnoczi wrote:
> > >
> > >
> > > - Suppose in the future there is also a kernel virtio-v
On Tue, Jan 23, 2018 at 06:01:15PM +0800, Jason Wang wrote:
>
>
> On 2018年01月23日 04:04, Michael S. Tsirkin wrote:
> > On Mon, Jan 22, 2018 at 12:17:51PM +, Stefan Hajnoczi wrote:
> > > On Mon, Jan 22, 2018 at 11:33:46AM +0800, Jason Wang wrote:
> > > > On 2018年01月19日 21:06, Stefan Hajnoczi wr
On 01/23/2018 07:12 PM, Stefan Hajnoczi wrote:
On Mon, Jan 22, 2018 at 07:09:06PM +0800, Wei Wang wrote:
On 01/19/2018 09:06 PM, Stefan Hajnoczi wrote:
- Suppose in the future there is also a kernel virtio-vhost-user driver as
other PCI devices, can we unbind the kernel driver first, and the
On Mon, Jan 22, 2018 at 07:09:06PM +0800, Wei Wang wrote:
> On 01/19/2018 09:06 PM, Stefan Hajnoczi wrote:
> Thanks for the quick implementation. Not sure if the following issues could
> be solved with this approach:
> - After we boot the slave VM, if we don't run the virtio-vhost-user driver
> (i
On 01/22/2018 08:17 PM, Stefan Hajnoczi wrote:
On Mon, Jan 22, 2018 at 11:33:46AM +0800, Jason Wang wrote:
On 2018年01月19日 21:06, Stefan Hajnoczi wrote:
Probably not for the following cases:
1) kick/call
I disagree here because kick/call is actually very efficient!
VM1's irqfd is the ioeventf
On Mon, Jan 22, 2018 at 10:04:18PM +0200, Michael S. Tsirkin wrote:
> On Mon, Jan 22, 2018 at 12:17:51PM +, Stefan Hajnoczi wrote:
> > On Mon, Jan 22, 2018 at 11:33:46AM +0800, Jason Wang wrote:
> > > On 2018年01月19日 21:06, Stefan Hajnoczi wrote:
> > > > These patches implement the virtio-vhost-
On 2018年01月23日 04:04, Michael S. Tsirkin wrote:
On Mon, Jan 22, 2018 at 12:17:51PM +, Stefan Hajnoczi wrote:
On Mon, Jan 22, 2018 at 11:33:46AM +0800, Jason Wang wrote:
On 2018年01月19日 21:06, Stefan Hajnoczi wrote:
These patches implement the virtio-vhost-user device design that I have
de
On Mon, Jan 22, 2018 at 12:17:51PM +, Stefan Hajnoczi wrote:
> On Mon, Jan 22, 2018 at 11:33:46AM +0800, Jason Wang wrote:
> > On 2018年01月19日 21:06, Stefan Hajnoczi wrote:
> > > These patches implement the virtio-vhost-user device design that I have
> > > described here:
> > > https://stefanha.
On Mon, Jan 22, 2018 at 11:33:46AM +0800, Jason Wang wrote:
> On 2018年01月19日 21:06, Stefan Hajnoczi wrote:
> > These patches implement the virtio-vhost-user device design that I have
> > described here:
> > https://stefanha.github.io/virtio/vhost-user-slave.html#x1-2830007
>
> Thanks for the patch
On 01/19/2018 09:06 PM, Stefan Hajnoczi wrote:
These patches implement the virtio-vhost-user device design that I have
described here:
https://stefanha.github.io/virtio/vhost-user-slave.html#x1-2830007
configure | 18 +
hw/virtio/Makefile.objs
On 2018年01月19日 21:06, Stefan Hajnoczi wrote:
These patches implement the virtio-vhost-user device design that I have
described here:
https://stefanha.github.io/virtio/vhost-user-slave.html#x1-2830007
Thanks for the patches, looks rather interesting and similar to split
device model used by X
The DPDK patch series is here:
http://dpdk.org/ml/archives/dev/2018-January/088155.html
These patches implement the virtio-vhost-user device design that I have
described here:
https://stefanha.github.io/virtio/vhost-user-slave.html#x1-2830007
The goal is to let the guest act as the vhost device backend for other guests.
This allows virtual networking and storage appliances to run ins
29 matches
Mail list logo
