Re: RFC: New device for zero-copy VM memory access

2019-11-26 Thread Dr. David Alan Gilbert
* Marc-André Lureau (marcandre.lur...@redhat.com) wrote: > Hi > > On Mon, Nov 4, 2019 at 4:05 PM wrote: > > > > > > > > On 2019-11-04 22:55, Dr. David Alan Gilbert wrote: > > > * ge...@hostfission.com (ge...@hostfission.com) wrote: > > >> > > >> > > >> On 2019-11-03 21:10, ge...@hostfission.com w

Re: RFC: New device for zero-copy VM memory access

2019-11-05 Thread Marc-André Lureau
Hi On Mon, Nov 4, 2019 at 4:05 PM wrote: > > > > On 2019-11-04 22:55, Dr. David Alan Gilbert wrote: > > * ge...@hostfission.com (ge...@hostfission.com) wrote: > >> > >> > >> On 2019-11-03 21:10, ge...@hostfission.com wrote: > >> > On 2019-11-01 02:52, Dr. David Alan Gilbert wrote: > >> > > * ge..

Re: RFC: New device for zero-copy VM memory access

2019-11-05 Thread Gerd Hoffmann
On Mon, Nov 04, 2019 at 09:31:47PM +1100, ge...@hostfission.com wrote: > > On 2019-11-04 21:26, Gerd Hoffmann wrote: > > Hi, > > > > > This new device, currently named `introspection` (which needs a more > > > suitable name, porthole perhaps?), provides a means of translating > > > guest physical

Re: RFC: New device for zero-copy VM memory access

2019-11-04 Thread Dr. David Alan Gilbert
* ge...@hostfission.com (ge...@hostfission.com) wrote: > > > On 2019-11-04 22:55, Dr. David Alan Gilbert wrote: > > * ge...@hostfission.com (ge...@hostfission.com) wrote: > > > > > > > > > On 2019-11-03 21:10, ge...@hostfission.com wrote: > > > > On 2019-11-01 02:52, Dr. David Alan Gilbert wrot

Re: RFC: New device for zero-copy VM memory access

2019-11-04 Thread geoff
On 2019-11-04 22:55, Dr. David Alan Gilbert wrote: * ge...@hostfission.com (ge...@hostfission.com) wrote: On 2019-11-03 21:10, ge...@hostfission.com wrote: > On 2019-11-01 02:52, Dr. David Alan Gilbert wrote: > > * ge...@hostfission.com (ge...@hostfission.com) wrote: > > > > > > > > > On 20

Re: RFC: New device for zero-copy VM memory access

2019-11-04 Thread Dr. David Alan Gilbert
* ge...@hostfission.com (ge...@hostfission.com) wrote: > > > On 2019-11-03 21:10, ge...@hostfission.com wrote: > > On 2019-11-01 02:52, Dr. David Alan Gilbert wrote: > > > * ge...@hostfission.com (ge...@hostfission.com) wrote: > > > > > > > > > > > > On 2019-11-01 01:52, Peter Maydell wrote: >

Re: RFC: New device for zero-copy VM memory access

2019-11-04 Thread geoff
On 2019-11-04 21:26, Gerd Hoffmann wrote: Hi, This new device, currently named `introspection` (which needs a more suitable name, porthole perhaps?), provides a means of translating guest physical addresses to host virtual addresses, and finally to the host offsets in RAM for file-backed mem

Re: RFC: New device for zero-copy VM memory access

2019-11-04 Thread Gerd Hoffmann
Hi, > This new device, currently named `introspection` (which needs a more > suitable name, porthole perhaps?), provides a means of translating > guest physical addresses to host virtual addresses, and finally to the > host offsets in RAM for file-backed memory guests. It does this by > means of

Re: RFC: New device for zero-copy VM memory access

2019-11-03 Thread geoff
On 2019-11-03 21:10, ge...@hostfission.com wrote: On 2019-11-01 02:52, Dr. David Alan Gilbert wrote: * ge...@hostfission.com (ge...@hostfission.com) wrote: On 2019-11-01 01:52, Peter Maydell wrote: > On Thu, 31 Oct 2019 at 14:26, wrote: > > As the author of Looking Glass, I also have to c

Re: RFC: New device for zero-copy VM memory access

2019-11-03 Thread geoff
On 2019-11-01 02:52, Dr. David Alan Gilbert wrote: * ge...@hostfission.com (ge...@hostfission.com) wrote: On 2019-11-01 01:52, Peter Maydell wrote: > On Thu, 31 Oct 2019 at 14:26, wrote: > > As the author of Looking Glass, I also have to consider the > > maintenance > > and the complexity

Re: RFC: New device for zero-copy VM memory access

2019-10-31 Thread Dr. David Alan Gilbert
* ge...@hostfission.com (ge...@hostfission.com) wrote: > > > On 2019-11-01 01:52, Peter Maydell wrote: > > On Thu, 31 Oct 2019 at 14:26, wrote: > > > As the author of Looking Glass, I also have to consider the > > > maintenance > > > and the complexity of implementing the vhost protocol into the

Re: RFC: New device for zero-copy VM memory access

2019-10-31 Thread geoff
On 2019-11-01 01:52, Peter Maydell wrote: On Thu, 31 Oct 2019 at 14:26, wrote: As the author of Looking Glass, I also have to consider the maintenance and the complexity of implementing the vhost protocol into the project. At this time a complete Porthole client can be implemented in 150 l

Re: RFC: New device for zero-copy VM memory access

2019-10-31 Thread Peter Maydell
On Thu, 31 Oct 2019 at 14:26, wrote: > As the author of Looking Glass, I also have to consider the maintenance > and the complexity of implementing the vhost protocol into the project. > At this time a complete Porthole client can be implemented in 150 lines > of C without external dependencies, a

Re: RFC: New device for zero-copy VM memory access

2019-10-31 Thread geoff
On 2019-11-01 00:24, Dr. David Alan Gilbert wrote: * ge...@hostfission.com (ge...@hostfission.com) wrote: Hi Dave, On 2019-10-31 05:52, Dr. David Alan Gilbert wrote: > * ge...@hostfission.com (ge...@hostfission.com) wrote: > > Hi All, > > > > Over the past week, I have been working to come u

Re: RFC: New device for zero-copy VM memory access

2019-10-31 Thread Dr. David Alan Gilbert
* ge...@hostfission.com (ge...@hostfission.com) wrote: > Hi Dave, > > On 2019-10-31 05:52, Dr. David Alan Gilbert wrote: > > * ge...@hostfission.com (ge...@hostfission.com) wrote: > > > Hi All, > > > > > > Over the past week, I have been working to come up with a solution > > > to the > > > memor

Re: RFC: New device for zero-copy VM memory access

2019-10-31 Thread Peter Maydell
On Thu, 31 Oct 2019 at 02:56, wrote: > If you still believe that vhost-user should be used, I will do what I > can to > implement it, but for such a simple device I honestly believe it is > overkill. While not making a statement on whether vhost-user is technically suitable in this case, I would

Re: RFC: New device for zero-copy VM memory access

2019-10-31 Thread geoff
Another update to this that adds support for unmap notification. The device has also been renamed to `porthole` and now resides here: https://github.com/gnif/qemu/blob/master/hw/misc/porthole.c And here is the updated Linux test client. https://gist.github.com/gnif/77e7fb54604b42a1a98ecb8bf3d2

Re: RFC: New device for zero-copy VM memory access

2019-10-30 Thread geoff
Hi Dave, On 2019-10-31 05:52, Dr. David Alan Gilbert wrote: * ge...@hostfission.com (ge...@hostfission.com) wrote: Hi All, Over the past week, I have been working to come up with a solution to the memory transfer performance issues that hinder the Looking Glass Project. Currently Looking G

Re: RFC: New device for zero-copy VM memory access

2019-10-30 Thread Dr. David Alan Gilbert
* ge...@hostfission.com (ge...@hostfission.com) wrote: > Hi All, > > Over the past week, I have been working to come up with a solution to the > memory transfer performance issues that hinder the Looking Glass Project. > > Currently Looking Glass works by using the IVSHMEM shared memory device >

Re: RFC: New device for zero-copy VM memory access

2019-10-30 Thread geoff
The windows driver source is now available also. https://github.com/gnif/Porthole-Guest-Driver I have also opted to rename the device to 'porthole', hopefully this name is acceptable. On 2019-10-30 09:53, ge...@hostfission.com wrote: Just to follow this up, here is a sample client application

Re: RFC: New device for zero-copy VM memory access

2019-10-29 Thread geoff
Just to follow this up, here is a sample client application for this device https://gist.github.com/gnif/77e7fb54604b42a1a98ecb8bf3d2cf46 -Geoff On 2019-10-30 01:31, ge...@hostfission.com wrote: Hi All, Over the past week, I have been working to come up with a solution to the memory transfe

RFC: New device for zero-copy VM memory access

2019-10-29 Thread geoff
Hi All, Over the past week, I have been working to come up with a solution to the memory transfer performance issues that hinder the Looking Glass Project. Currently Looking Glass works by using the IVSHMEM shared memory device which is fed by an application that captures the guest's video o