Re: [Qemu-devel] [RFC PATCH 0/4] ARM/ARM64 fixes for live memory snapshot based on userfaultfd

Hello Alan, On 09/03/2017 18:46, Dr. David Alan Gilbert wrote: * Christian Pinto (c.pi...@virtualopensystems.com) wrote: This patch series introduces a set of fixes to the previous work proposed by Hailiang Zhang to enable in QEMU live memory snapshot based on userfaultfd. See discussion here

[Qemu-devel] [RFC PATCH 2/4] migration/ram: Fix for ARM/ARM64 page size

Architecture such as ARM use a page size of 1KB, while write protection is done at the granularity of host pages (generally 4KB). All addresses must always be aligned to the size of a host page. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Signed-off-by: Baptiste Reynal

[Qemu-devel] [RFC PATCH 3/4] migration: snapshot thread

VM execution was resumed while migration was still in setup. This was causing a bus error because the userfault thread was waking up VM too early during migration setup. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Signed-off-by: Baptiste Reynal <b.rey...@virtualopensy

[Qemu-devel] [RFC PATCH 4/4] migration/postcopy-ram: ram_set_pages_wp fix

setting UFFDIO_WRITEPROTECT_MODE_DONTWAKE when write un-protecting a page does not wake up the faulting thread. Set to 0 to force the faulting (VM) thread to wake-up. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Signed-off-by: Baptiste Reynal <b.rey...@virtualopensy

[Qemu-devel] [RFC PATCH 1/4] migration/postcopy-ram: check pagefault flags in userfaultfd thread

The UFFD_PAGEFAULT_FLAG_WP should be set every time the page fault is due to a write to a write-protected page. Flag should be checked at every time to be sure the page fault is due to a write into WP area. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Signed-off-by: Ba

[Qemu-devel] [RFC PATCH 0/4] ARM/ARM64 fixes for live memory snapshot based on userfaultfd

-m 256 -kernel Image \ -initrd rootfs.cpio.gz \ -append "earlyprintk rw console=ttyAMA0" \ -net nic -net user \ -nographic -serial stdio -monitor pty \ -incoming file:/root/test_snapshot Christian Pinto (4): migration/postcopy-ram: check

Re: [Qemu-devel] [RFC 00/13] Live memory snapshot based on userfaultfd

Thanks a lot Hailiang On 28/02/2017 02:48, Hailiang Zhang wrote: Hi, On 2017/2/27 23:37, Christian Pinto wrote: Hello Hailiang, are there any updates on this patch series? Are you planning to release a new version? No, userfaultfd still does not support write-protect for KVM. You can see

Re: [Qemu-devel] [RFC 00/13] Live memory snapshot based on userfaultfd

Hello Hailiang, are there any updates on this patch series? Are you planning to release a new version? You say there are some issues with the current snapshot-v2 version, which issues were you referring to? On my side the only problem I have seen was that the live snapshot was not working

Re: [Qemu-devel] [virtio-dev][RFC v3] virtio-sdm: new device specification

Hello Edgar, sorry for the delay. On 08/09/2016 17:38, Edgar E. Iglesias wrote: On Thu, Sep 08, 2016 at 09:06:00AM +0200, Christian Pinto wrote: Hello Edgar, On 07/09/2016 18:02, Edgar E. Iglesias wrote: On Wed, Sep 07, 2016 at 05:39:08PM +0200, Christian Pinto wrote: On 07/09/2016 09

Re: [Qemu-devel] [virtio-dev][RFC v3] virtio-sdm: new device specification

Hello Edgar, On 07/09/2016 18:02, Edgar E. Iglesias wrote: On Wed, Sep 07, 2016 at 05:39:08PM +0200, Christian Pinto wrote: On 07/09/2016 09:51, Edgar E. Iglesias wrote: On Wed, Sep 07, 2016 at 09:24:39AM +0200, Christian Pinto wrote: Hello Edgar, thanks for your comments. Thanks

Re: [Qemu-devel] [virtio-dev][RFC v3] virtio-sdm: new device specification

On 07/09/2016 09:51, Edgar E. Iglesias wrote: On Wed, Sep 07, 2016 at 09:24:39AM +0200, Christian Pinto wrote: Hello Edgar, thanks for your comments. Thanks for the clarification, I have a few follow-up questions/comments. On 06/09/2016 23:43, Edgar E. Iglesias wrote: Hi, Sorry

Re: [Qemu-devel] [virtio-dev][RFC v3] virtio-sdm: new device specification

more clear. Thanks, Christian Best regards, Edgar On Tue, Aug 30, 2016 at 01:22:26PM +0200, Christian Pinto wrote: Hello, are there any comments? Christian On 09/08/2016 09:37, Christian Pinto wrote: This patch adds the specification of the Signal Dristribution Module virtio device to t

Re: [Qemu-devel] [virtio-dev][RFC v3] virtio-sdm: new device specification

Hello, are there any comments? Christian On 09/08/2016 09:37, Christian Pinto wrote: This patch adds the specification of the Signal Dristribution Module virtio device to the current virtio specification document. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Sign

[Qemu-devel] [virtio-dev][RFC v3] virtio-sdm: new device specification

This patch adds the specification of the Signal Dristribution Module virtio device to the current virtio specification document. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Signed-off-by: Baptiste Reynal <b.rey...@virtualopensystems.com> --- v2 -> v3: - Remov

Re: [Qemu-devel] [virtio-dev][RFC v2 2/2] virtio-sdm: new device specification

Hello Stefan, thanks for the feedback.I will rework the specification and send a v3 patch series. Christian On Thu, Aug 4, 2016 at 10:46 AM, Stefan Hajnoczi <stefa...@redhat.com> wrote: > On Fri, Jul 22, 2016 at 06:18:25PM +0200, Christian Pinto wrote: > > Hello Stefan, > &g

Re: [Qemu-devel] [virtio-dev][RFC v2 2/2] virtio-sdm: new device specification

Hello Stefan, On Tue, Jul 19, 2016 at 10:40 AM, Stefan Hajnoczi <stefa...@redhat.com> wrote: > On Tue, Jul 19, 2016 at 09:47:13AM +0200, Christian Pinto wrote: > > > > +During the initialization phase the device connects also to the > > > communication > &

Re: [Qemu-devel] [virtio-dev][RFC v2 2/2] virtio-sdm: new device specification

Hello Stefan, thanks for your comments. On Thu, Jul 14, 2016 at 2:17 PM, Stefan Hajnoczi <stefa...@gmail.com> wrote: > On Tue, Jun 28, 2016 at 01:03:44PM +0200, Christian Pinto wrote: > > This patch adds the specification of the Signal Dristribution Module > virtio > &g

Re: [Qemu-devel] [virtio-dev] Re: [RFC v3 0/6] SDM Interface

Thanks a lot Stefan. Looking forward for your feedback. Christian On Thu, Jun 30, 2016 at 10:47 AM, Stefan Hajnoczi <stefa...@redhat.com> wrote: > On Thu, Jun 30, 2016 at 10:26:56AM +0200, Christian Pinto wrote: > > Ping... > > > > are there any comments? > &g

Re: [Qemu-devel] [RFC v3 0/6] SDM Interface

Ping... are there any comments? Thanks, Christian On Fri, Jun 17, 2016 at 5:54 PM, Christian Pinto < c.pi...@virtualopensystems.com> wrote: > This patch series introduces a new device to QEMU, the SDM (Signal > Distribution > Module), > intended to route inter-proce

[Qemu-devel] [virtio-dev][RFC v2 2/2] virtio-sdm: new device specification

This patch adds the specification of the Signal Dristribution Module virtio device to the current virtio specification document. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Signed-off-by: Baptiste Reynal <b.rey...@virtualopensystems.com> --- v1 -> v2: - F

[Qemu-devel] [virtio-dev][RFC v2 1/2] content: reserve virtio device ID

Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Signed-off-by: Baptiste Reynal <b.rey...@virtualopensystems.com> --- v1 -> v2: - removed edit including virtio-sdm specs text --- content.tex | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content.tex b/co

[Qemu-devel] [virtio-dev][RFC v2 0/2] Signal Distribution Module virtio device specification

since v1: - Fixed some typos - Removed dependencies from QEMU - Added explanation on how SDM can be used in AMP systems - Explained semantics of payload field in SDMSignalData struct --- Christian Pinto (2): content: reserve virtio device ID virtio-sdm: new device specification content.tex

Re: [Qemu-devel] [virtio-dev][RFC 1/2] content: reserve virtio device ID

On Fri, Jun 24, 2016 at 3:04 PM, Cornelia Huck <cornelia.h...@de.ibm.com> wrote: > On Fri, 24 Jun 2016 14:45:29 +0200 > Christian Pinto <c.pi...@virtualopensystems.com> wrote: > > > On Thu, Jun 23, 2016 at 8:57 PM, Stefan Hajnoczi <stefa...@redhat.com> > >

Re: [Qemu-devel] [virtio-dev][RFC 1/2] content: reserve virtio device ID

Hello Stefan, On Thu, Jun 23, 2016 at 8:57 PM, Stefan Hajnoczi <stefa...@redhat.com> wrote: > On Fri, Jun 17, 2016 at 06:03:13PM +0200, Christian Pinto wrote: > > Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> > > --- > > content.tex | 4

Re: [Qemu-devel] [virtio-dev][RFC 2/2] virtio-sdm: new device specification

Hello Stefan, On Thu, Jun 23, 2016 at 9:39 PM, Stefan Hajnoczi <stefa...@redhat.com> wrote: > On Fri, Jun 17, 2016 at 06:03:14PM +0200, Christian Pinto wrote: > > This patch adds the specification of the Signal Dristribution Module > virtio > > device to the current virti

[Qemu-devel] [virtio-dev][RFC 2/2] virtio-sdm: new device specification

This patch adds the specification of the Signal Dristribution Module virtio device to the current virtio specification document. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- virtio-sdm.tex | 126 + 1 file change

[Qemu-devel] [virtio-dev][RFC 0/2] Signal Distribution Module virtio device specification

Christian Pinto (2): content: reserve virtio device ID virtio-sdm: new device specification content.tex| 4 ++ virtio-sdm.tex | 126 + 2 files changed, 130 insertions(+) create mode 100644 virtio-sdm.tex -- 1.9.1

[Qemu-devel] [virtio-dev][RFC 1/2] content: reserve virtio device ID

Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- content.tex | 4 1 file changed, 4 insertions(+) diff --git a/content.tex b/content.tex index d989d98..0d98926 100644 --- a/content.tex +++ b/content.tex @@ -2990,6 +2990,8 @@ Device ID & Virtio Device\\

[Qemu-devel] [RFC v3 4/6] hw/misc: sdm virtio device

master is true, specifies the number of slaves len-signals=[signals_number] - specifies the number of signals signals[x]=[signal_id] - add a signal to the device, with the ID x Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Signed-off-by: Baptiste Reynal <b.rey...@virtual

[Qemu-devel] [RFC v3 5/6] hw/misc: sdm communication local

<b.rey...@virtualopensystems.com> Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- v2 -> v3: - added sdm_local_update_num_slaves to local communication channel - realloc slaves array in case of max slaves change - fixed bug: signal notifications not sent to correct sdm device

[Qemu-devel] [RFC v3 1/6] hw/misc: sdm interface

signal is received (for example to boot the machine). Signed-off-by: Baptiste Reynal <b.rey...@virtualopensystems.com> Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- v2 -> v3: - Added sdm_device_set_num_slaves function to sdm-device class - Added sdm_communication_upd

[Qemu-devel] [RFC v3 0/6] SDM Interface

This patch series introduces a new device to QEMU, the SDM (Signal Distribution Module), intended to route inter-processor signals intra and inter QEMU instances. To be as modular as possible, the device is split between the interface (virtio/platform) and the communication channel

[Qemu-devel] [RFC v3 3/6] hw/arm: sysbus-fdt

From: Baptiste Reynal <b.rey...@virtualopensystems.com> Added node creation for dynamically instantiated sysbus SDM device. Support added for all ARM machines modeling dynamic sysbus devices instantiation. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> Signed-off-

[Qemu-devel] [RFC v3 2/6] hw/misc: sdm platform device

number] - if master is true, specifies the number of slaves len-signals=[signals_number] - specifies the number of signals signals[x]=[signal_id] - add a signal to the device, with the ID x Signed-off-by: Baptiste Reynal <b.rey...@virtualopensystems.com> Signed-off-by: Christian

[Qemu-devel] [RFC v3 6/6] hw/misc: sdm communication socket

[RFC v2 1/1] backend: multi-client-socket" Signed-off-by: Baptiste Reynal <b.rey...@virtualopensystems.com> Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- v2 -> v3: - added sdm_socket_update_num_slaves to socket based communication channel - realloc slaves array i

Re: [Qemu-devel] [virtio-dev] New virtio device specification

Hello Cornelia, thanks for this clarification. I will immediately start looking into this and soon release the two patches. Best, Christian On Fri, Jun 10, 2016 at 10:15 AM, Cornelia Huck <cornelia.h...@de.ibm.com> wrote: > On Fri, 10 Jun 2016 10:01:05 +0200 > Christian

[Qemu-devel] [virtio-dev] New virtio device specification

Hi all, we are working on a new virtio device, namely the Signal Distribution Module (SDM). The SDM routes inter-processor signals intra and inter QEMU instances, using a user-defined communication channel. At the current state the SDM provides a local channel, for intra-QEMU signals, and a

Re: [Qemu-devel] [RFC PATCH 0/8] Towards an Heterogeneous QEMU

Hello Peter, Apologies for the highly delayed response. On Nov 13, 2015 08:02, "Peter Crosthwaite" <crosthwaitepe...@gmail.com> wrote: > > Hi Christian, > > Sorry about the delayed response. > > On Tue, Oct 27, 2015 at 3:30 AM, Christian Pinto <

Re: [Qemu-devel] [RFC PATCH 0/8] Towards an Heterogeneous QEMU

On 25/10/2015 22:38, Peter Crosthwaite wrote: On Thu, Oct 22, 2015 at 2:21 AM, Christian Pinto <c.pi...@virtualopensystems.com> wrote: Hello Peter, On 07/10/2015 17:48, Peter Crosthwaite wrote: On Mon, Oct 5, 2015 at 8:50 AM, Christian Pinto <c.pi...@virtualopensystems.com> w

Re: [Qemu-devel] [RFC PATCH 0/8] Towards an Heterogeneous QEMU

Hello Peter, On 07/10/2015 17:48, Peter Crosthwaite wrote: On Mon, Oct 5, 2015 at 8:50 AM, Christian Pinto <c.pi...@virtualopensystems.com> wrote: Hello Peter, thanks for your comments On 01/10/2015 18:26, Peter Crosthwaite wrote: On Tue, Sep 29, 2015 at 6:57 AM, Christian Pinto

Re: [Qemu-devel] [RFC PATCH 0/8] Towards an Heterogeneous QEMU

Hello Peter, thanks for your comments On 01/10/2015 18:26, Peter Crosthwaite wrote: On Tue, Sep 29, 2015 at 6:57 AM, Christian Pinto <c.pi...@virtualopensystems.com> wrote: Hi all, This RFC patch-series introduces the set of changes enabling the architectural elements to

[Qemu-devel] [RFC PATCH 4/8] hw/misc: IDM Device

backend socket=[socket_id] - id of the multi-client socket Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- default-configs/arm-softmmu.mak| 1 + default-configs/i386-softmmu.mak | 1 + default-configs/x86_64-softmmu.mak | 1 + hw/misc/Makefil

[Qemu-devel] [RFC PATCH 7/8] hw/arm: boot

model executed. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- hw/arm/boot.c | 13 + 1 file changed, 13 insertions(+) diff --git a/hw/arm/boot.c b/hw/arm/boot.c index bef451b..ee0c4a1 100644 --- a/hw/arm/boot.c +++ b/hw/arm/boot.c @@ -590,6 +590,19 @@ stati

[Qemu-devel] [RFC PATCH 2/8] backend: shared memory backend

From: Baptiste Reynal This patch introduces a shared memory backend, allowing to share memory between a master and many slaves. The memory is implemented using hugetlbfs, and relies on the multi-socket backend to share informations (size and offset for the

[Qemu-devel] [RFC PATCH 6/8] qemu: slave machine flag

This patch adds a new machine flag, to configure qemu as a slave instance. Usage -machine -slave=[on|off] (default=off) Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- hw/core/machine.c | 27 +++ include/hw/boards.h | 2 ++ qemu-opti

[Qemu-devel] [RFC PATCH 0/8] Towards an Heterogeneous QEMU

d memory backend migration: add shared migration type Christian Pinto (5): hw/misc: IDM Device hw/arm: sysbus-fdt qemu: slave machine flag hw/arm: boot qemu: numa backends/Makefile.objs | 4 +- backends/hostmem-shared.c | 203 +

[Qemu-devel] [RFC PATCH 1/8] backend: multi-socket

From: Baptiste Reynal This patch introduces a new socket for QEMU, called multi-socket. This socket allows multiple QEMU instances to communicate by sharing messages and file descriptors. A socket can be instantiated with the following parameters: -object

[Qemu-devel] [RFC PATCH 5/8] hw/arm: sysbus-fdt

Added node creation for dynamically instantiated sysbus IDM device. Support added for all ARM machines modeling dynamic sysbus devices instantiation. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- hw/arm/sysbus-fdt.

[Qemu-devel] [RFC PATCH 8/8] qemu: numa

.) and vmstate_register would fail. The patch skips the call to vmstate_register in case of slave shared memory backend, that will be performed later after the actual memory pointer is available. Signed-off-by: Christian Pinto <c.pi...@virtualopensystems.com> --- numa.c | 17 ++

[Qemu-devel] [RFC PATCH 3/8] migration: add shared migration type

From: Baptiste Reynal A QEMU instance can now wait for the instantiation of the memory by the master while shared-memory backend is used. Use: -incoming "shared:" Signed-off-by: Baptiste Reynal --- backends/hostmem-shared.c

Re: [Qemu-devel] [RFC] Towards an Heterogeneous QEMU

Hello Paolo, On 31/07/2015 15:10, Paolo Bonzini wrote: On 27/07/2015 15:54, Christian Pinto wrote: From the user point of view there is usually an operating system booting on the Master processor (e.g. Linux) at platform startup, while the other processors are used to offload the Master one

Re: [Qemu-devel] [RFC] Towards an Heterogeneous QEMU

Hello Cristopher, On 31/07/2015 14:03, Christopher Covington wrote: Hi Christian, On 07/27/2015 09:54 AM, Christian Pinto wrote: Hi all, this message is to present, and get feedback, on a QEMU enhancement which we are working on. Most of the state-of-the-art SoCs use the heterogeneous

[Qemu-devel] [RFC] Towards an Heterogeneous QEMU

Hi all, this message is to present, and get feedback, on a QEMU enhancement which we are working on. Most of the state-of-the-art SoCs use the heterogeneous paradigm, in which a Master processor is surrounded by multiple (Slave) co- processors (other CPUs, MCUs, hardware accelerators, etc)