[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 COLOPre 03/13] libxc/restore: zero ioreq page only one time
> -----Original Message----- > From: Yang Hongyang [mailto:yanghy@xxxxxxxxxxxxxx] > Sent: 11 June 2015 13:59 > To: Paul Durrant; Wen Congyang; Andrew Cooper; xen-devel@xxxxxxxxxxxxx > Cc: Wei Liu; Ian Campbell; guijianfeng@xxxxxxxxxxxxxx; > yunhong.jiang@xxxxxxxxx; Eddie Dong; rshriram@xxxxxxxxx; Ian Jackson > Subject: Re: [Xen-devel] [PATCH v2 COLOPre 03/13] libxc/restore: zero ioreq > page only one time > > > > On 06/11/2015 06:20 PM, Paul Durrant wrote: > >> -----Original Message----- > >> From: Wen Congyang [mailto:wency@xxxxxxxxxxxxxx] > >> Sent: 11 June 2015 09:48 > >> To: Paul Durrant; Andrew Cooper; Yang Hongyang; xen- > devel@xxxxxxxxxxxxx > >> Cc: Wei Liu; Ian Campbell; guijianfeng@xxxxxxxxxxxxxx; > [...] > > > >> > >> In our implementation, we don't start a new emulator. The codes can > work, > >> but some bugs may be not triggered. > >> > > > > How do you reconcile the incoming QEMU save record with the running > emulator state? > > We introduce a qmp command "xen-load-devices- > state"(libxl__qmp_restore) which > can restore the emulator state. The step of resotre emulator state at a > checkpoint is: > > 1. libxl__qmp_stop -> vm_stop() in qemu > 2. libxl__qmp_restore -> load_vmstate() in qemu > 3. libxl__qmp_resume -> vm_start() in qemu > Ok, that sounds like the ideal time to hook back into Xen by creating a new ioreq server. Paul > > > > Paul > > > >> Thanks > >> Wen Congyang > >> > >>> > >>> Paul > >>> > >>>> > >>>> Thanks > >>>> Wen Congyang > >>>> > >>>>> > >>>>> Paul > >>>>> > >>>>>> We will set to the guest to a new state, the old state should be > >> dropped. > >>>>>> > >>>>>> Thanks > >>>>>> Wen Congyang > >>>>>> > >>>>>>> > >>>>>>> Paul > >>>>>>> > >>>>>>>> > >>>>>>>> Thanks > >>>>>>>> Wen Congyang > >>>>>>>> > >>>>>>>>> > >>>>>>>>> Paul > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>> Thanks > >>>>>>>>>> Wen Congyang > >>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> ~Andrew > >>>>>>>>>>> . > >>>>>>>>>>> > >>>>>>>>> > >>>>>>>>> . > >>>>>>>>> > >>>>>>> > >>>>>>> . > >>>>>>> > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Xen-devel mailing list > >>>>>> Xen-devel@xxxxxxxxxxxxx > >>>>>> http://lists.xen.org/xen-devel > >>>>> > >>>>> _______________________________________________ > >>>>> Xen-devel mailing list > >>>>> Xen-devel@xxxxxxxxxxxxx > >>>>> http://lists.xen.org/xen-devel > >>>>> . > >>>>> > >>> > >>> . > >>> > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@xxxxxxxxxxxxx > > http://lists.xen.org/xen-devel > > . > > > > -- > Thanks, > Yang. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |