Re: [Xen-devel] [PATCH v3] xen: don't save/restore the physmap on VM save/restore

2017-03-14 Thread Stefano Stabellini
On Tue, 14 Mar 2017, Igor Druzhinin wrote: > On 13/03/17 21:15, Stefano Stabellini wrote: > > On Mon, 13 Mar 2017, Igor Druzhinin wrote: > >> Saving/restoring the physmap to/from xenstore was introduced to > >> QEMU majorly in order to cover up the VRAM region restore issue. > >> The sequence of

Re: [Xen-devel] [PATCH v3] xen: don't save/restore the physmap on VM save/restore

2017-03-13 Thread Igor Druzhinin
On 13/03/17 21:15, Stefano Stabellini wrote: > On Mon, 13 Mar 2017, Igor Druzhinin wrote: >> Saving/restoring the physmap to/from xenstore was introduced to >> QEMU majorly in order to cover up the VRAM region restore issue. >> The sequence of restore operations implies that we should know >> the

Re: [Xen-devel] [PATCH v3] xen: don't save/restore the physmap on VM save/restore

2017-03-13 Thread Stefano Stabellini
On Mon, 13 Mar 2017, Igor Druzhinin wrote: > Saving/restoring the physmap to/from xenstore was introduced to > QEMU majorly in order to cover up the VRAM region restore issue. > The sequence of restore operations implies that we should know > the effective guest VRAM address *before* we have the