Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-30 Thread Wang, Wei W
On Sunday, January 29, 2017 10:14 PM, Jan Kiszka wrote: > On 2017-01-29 15:00, Marc-André Lureau wrote: > > Hi > > > > On Sun, Jan 29, 2017 at 12:44 PM Jan Kiszka > > wrote: > > > > >> Of course, I'm careful with investing much time into expanding

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-30 Thread Jan Kiszka
On 2017-01-30 13:19, Markus Armbruster wrote: >>> Can you explain why not letting the guest map the shared memory into its >>> address space on its own just like any other piece of device memory is a >>> requirement? >> >> It requires reconfiguration of the sensitive 2nd level page tables >>

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-30 Thread Markus Armbruster
Jan Kiszka writes: > On 2017-01-30 09:00, Markus Armbruster wrote: >> Jan Kiszka writes: >> >>> On 2017-01-27 20:36, Markus Armbruster wrote: Jan Kiszka writes: > On 2017-01-23 15:19, Markus Armbruster wrote: >> Jan

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-30 Thread Stefan Hajnoczi
On Sun, Jan 29, 2017 at 12:56:23PM +0100, msuchanek wrote: > On 2017-01-17 10:59, Stefan Hajnoczi wrote: > > On Mon, Jan 16, 2017 at 02:10:17PM +0100, Jan Kiszka wrote: > > > On 2017-01-16 13:41, Marc-André Lureau wrote: > > > > On Mon, Jan 16, 2017 at 12:37 PM Jan Kiszka

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-30 Thread Jan Kiszka
On 2017-01-30 09:00, Markus Armbruster wrote: > Jan Kiszka writes: > >> On 2017-01-27 20:36, Markus Armbruster wrote: >>> Jan Kiszka writes: >>> On 2017-01-23 15:19, Markus Armbruster wrote: > Jan Kiszka writes: >

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-30 Thread Jan Kiszka
On 2017-01-30 09:02, Markus Armbruster wrote: > Jan Kiszka writes: > >> On 2017-01-29 15:00, Marc-André Lureau wrote: >>> Hi >>> >>> On Sun, Jan 29, 2017 at 12:44 PM Jan Kiszka >> > wrote: >>> >>> >> Of course, I'm careful with

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-30 Thread Markus Armbruster
Jan Kiszka writes: > On 2017-01-29 15:00, Marc-André Lureau wrote: >> Hi >> >> On Sun, Jan 29, 2017 at 12:44 PM Jan Kiszka > > wrote: >> >> >> Of course, I'm careful with investing much time into expanding the >> >>

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-30 Thread Markus Armbruster
Jan Kiszka writes: > On 2017-01-27 20:36, Markus Armbruster wrote: >> Jan Kiszka writes: >> >>> On 2017-01-23 15:19, Markus Armbruster wrote: Jan Kiszka writes: > Hi, > > some of you may know that we are using

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-29 Thread Jan Kiszka
On 2017-01-29 15:00, Marc-André Lureau wrote: > Hi > > On Sun, Jan 29, 2017 at 12:44 PM Jan Kiszka > wrote: > > >> Of course, I'm careful with investing much time into expanding the > >> existing, for Jailhouse possibly sufficient design if

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-29 Thread Marc-André Lureau
Hi On Sun, Jan 29, 2017 at 12:44 PM Jan Kiszka wrote: > >> Of course, I'm careful with investing much time into expanding the > >> existing, for Jailhouse possibly sufficient design if there no real > >> interest in continuing the ivshmem support in QEMU - because of > >>

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-29 Thread msuchanek
On 2017-01-17 10:59, Stefan Hajnoczi wrote: On Mon, Jan 16, 2017 at 02:10:17PM +0100, Jan Kiszka wrote: On 2017-01-16 13:41, Marc-André Lureau wrote: > On Mon, Jan 16, 2017 at 12:37 PM Jan Kiszka > wrote: > So, this is our proposal.

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-29 Thread Jan Kiszka
On 2017-01-27 20:36, Markus Armbruster wrote: > Jan Kiszka writes: > >> On 2017-01-23 15:19, Markus Armbruster wrote: >>> Jan Kiszka writes: >>> Hi, some of you may know that we are using a shared memory device similar to ivshmem in

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-27 Thread Markus Armbruster
Jan Kiszka writes: > On 2017-01-23 15:19, Markus Armbruster wrote: >> Jan Kiszka writes: >> >>> Hi, >>> >>> some of you may know that we are using a shared memory device similar to >>> ivshmem in the partitioning hypervisor Jailhouse [1]. >>> >>> We

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-25 Thread Jan Kiszka
On 2017-01-23 15:19, Markus Armbruster wrote: > Jan Kiszka writes: > >> Hi, >> >> some of you may know that we are using a shared memory device similar to >> ivshmem in the partitioning hypervisor Jailhouse [1]. >> >> We started as being compatible to the original ivshmem

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-23 Thread Markus Armbruster
Jan Kiszka writes: > Hi, > > some of you may know that we are using a shared memory device similar to > ivshmem in the partitioning hypervisor Jailhouse [1]. > > We started as being compatible to the original ivshmem that QEMU > implements, but we quickly deviated in some

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-23 Thread Måns Rullgård
"Wang, Wei W" writes: > On Saturday, January 21, 2017 12:38 AM, Jan Kiszka wrote: >> On 2017-01-20 12:54, Wang, Wei W wrote: >>> Having a theoretical analysis on the performance: The traditional >>> shared memory mechanism, sharing an intermediate memory, requires 2 >>>

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-22 Thread Wang, Wei W
On Saturday, January 21, 2017 12:38 AM, Jan Kiszka wrote: > On 2017-01-20 12:54, Wang, Wei W wrote: > > On Tuesday, January 17, 2017 5:46 PM, Jan Kiszka wrote: > >> On 2017-01-17 10:13, Wang, Wei W wrote: > >>> Hi Jan, > >>> > >>> On Monday, January 16, 2017 9:10 PM, Jan Kiszka wrote: > On

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-20 Thread Jan Kiszka
On 2017-01-20 12:54, Wang, Wei W wrote: > On Tuesday, January 17, 2017 5:46 PM, Jan Kiszka wrote: >> On 2017-01-17 10:13, Wang, Wei W wrote: >>> Hi Jan, >>> >>> On Monday, January 16, 2017 9:10 PM, Jan Kiszka wrote: On 2017-01-16 13:41, Marc-André Lureau wrote: > On Mon, Jan 16, 2017 at

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-20 Thread Wang, Wei W
On Tuesday, January 17, 2017 5:46 PM, Jan Kiszka wrote: > On 2017-01-17 10:13, Wang, Wei W wrote: > > Hi Jan, > > > > On Monday, January 16, 2017 9:10 PM, Jan Kiszka wrote: > >> On 2017-01-16 13:41, Marc-André Lureau wrote: > >>> On Mon, Jan 16, 2017 at 12:37 PM Jan Kiszka

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-17 Thread Jan Kiszka
On 2017-01-17 10:59, Stefan Hajnoczi wrote: > On Mon, Jan 16, 2017 at 02:10:17PM +0100, Jan Kiszka wrote: >> On 2017-01-16 13:41, Marc-André Lureau wrote: >>> On Mon, Jan 16, 2017 at 12:37 PM Jan Kiszka >> > wrote: >>> So, this is our

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-17 Thread Stefan Hajnoczi
On Mon, Jan 16, 2017 at 03:34:58PM +0100, Jan Kiszka wrote: > On 2017-01-16 15:18, Stefan Hajnoczi wrote: > > On Mon, Jan 16, 2017 at 09:36:51AM +0100, Jan Kiszka wrote: > >> some of you may know that we are using a shared memory device similar to > >> ivshmem in the partitioning hypervisor

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-17 Thread Stefan Hajnoczi
On Mon, Jan 16, 2017 at 02:10:17PM +0100, Jan Kiszka wrote: > On 2017-01-16 13:41, Marc-André Lureau wrote: > > On Mon, Jan 16, 2017 at 12:37 PM Jan Kiszka > > wrote: > > So, this is our proposal. Would be great to hear some opinions if

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-17 Thread Jan Kiszka
On 2017-01-17 10:13, Wang, Wei W wrote: > Hi Jan, > > On Monday, January 16, 2017 9:10 PM, Jan Kiszka wrote: >> On 2017-01-16 13:41, Marc-André Lureau wrote: >>> On Mon, Jan 16, 2017 at 12:37 PM Jan Kiszka >> > wrote: >>> some of you may

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-17 Thread Wang, Wei W
Hi Jan, On Monday, January 16, 2017 9:10 PM, Jan Kiszka wrote: > On 2017-01-16 13:41, Marc-André Lureau wrote: > > On Mon, Jan 16, 2017 at 12:37 PM Jan Kiszka > > wrote: > > some of you may know that we are using a shared memory device

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-16 Thread Jan Kiszka
On 2017-01-16 15:18, Stefan Hajnoczi wrote: > On Mon, Jan 16, 2017 at 09:36:51AM +0100, Jan Kiszka wrote: >> some of you may know that we are using a shared memory device similar to >> ivshmem in the partitioning hypervisor Jailhouse [1]. >> >> We started as being compatible to the original

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-16 Thread Stefan Hajnoczi
On Mon, Jan 16, 2017 at 09:36:51AM +0100, Jan Kiszka wrote: > some of you may know that we are using a shared memory device similar to > ivshmem in the partitioning hypervisor Jailhouse [1]. > > We started as being compatible to the original ivshmem that QEMU > implements, but we quickly deviated

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-16 Thread Jan Kiszka
Hi Marc-André, On 2017-01-16 13:41, Marc-André Lureau wrote: > Hi > > On Mon, Jan 16, 2017 at 12:37 PM Jan Kiszka > wrote: > > Hi, > > some of you may know that we are using a shared memory device similar to > ivshmem in the

Re: [Qemu-devel] Towards an ivshmem 2.0?

2017-01-16 Thread Marc-André Lureau
Hi On Mon, Jan 16, 2017 at 12:37 PM Jan Kiszka wrote: > Hi, > > some of you may know that we are using a shared memory device similar to > ivshmem in the partitioning hypervisor Jailhouse [1]. > > We started as being compatible to the original ivshmem that QEMU >

[Qemu-devel] Towards an ivshmem 2.0?

2017-01-16 Thread Jan Kiszka
Hi, some of you may know that we are using a shared memory device similar to ivshmem in the partitioning hypervisor Jailhouse [1]. We started as being compatible to the original ivshmem that QEMU implements, but we quickly deviated in some details, and in the recent months even more. Some of the