search for: stopcmd

...ably I haven't fully understood it. Please see the example > below: > > 1) host-to-guest ctrl_vq: > StartCMD, ID=1 > > 2) guest-to-host free_page_vq: > free_page, ID=1 > free_page, ID=1 > free_page, ID=1 > free_page, ID=1 > > 3) host-to-guest ctrl_vq: > StopCMD, ID=1 > > 4) initiate the 2nd try of live migration via host-to-guest ctrl_vq: > StartCMD, ID=2 > > 5) the guest-to-host free_page_vq might look like this: > free_page, ID=1 > free_page, ID=1 > free_page, ID=2 > free_page, ID=2 > > The device will need to drop (p...

...ably I haven't fully understood it. Please see the example > below: > > 1) host-to-guest ctrl_vq: > StartCMD, ID=1 > > 2) guest-to-host free_page_vq: > free_page, ID=1 > free_page, ID=1 > free_page, ID=1 > free_page, ID=1 > > 3) host-to-guest ctrl_vq: > StopCMD, ID=1 > > 4) initiate the 2nd try of live migration via host-to-guest ctrl_vq: > StartCMD, ID=2 > > 5) the guest-to-host free_page_vq might look like this: > free_page, ID=1 > free_page, ID=1 > free_page, ID=2 > free_page, ID=2 > > The device will need to drop (p...

...notification, Guest reads the Host2Guest > register, and detaches all the used buffers from free_page_vq; > (then for each StartCMD, the free_page_vq will always have no obsolete free > page hints, right? ) > > 4) Guest start report free pages: > 4.1) Host may actively write StopCMD to the Host2Guest register before > the guest finishes; or > 4.2) Guest finishes reporting, write StopCMD the Guest2HOST register, > which traps to QEMU, to stop. > > > Best, > Wei I am not sure it matters whether a VQ or the config are used to start/stop. But I think f...

...notification, Guest reads the Host2Guest > register, and detaches all the used buffers from free_page_vq; > (then for each StartCMD, the free_page_vq will always have no obsolete free > page hints, right? ) > > 4) Guest start report free pages: > 4.1) Host may actively write StopCMD to the Host2Guest register before > the guest finishes; or > 4.2) Guest finishes reporting, write StopCMD the Guest2HOST register, > which traps to QEMU, to stop. > > > Best, > Wei I am not sure it matters whether a VQ or the config are used to start/stop. But I think f...

...n receiving a configuration notification, Guest reads the Host2Guest register, and detaches all the used buffers from free_page_vq; (then for each StartCMD, the free_page_vq will always have no obsolete free page hints, right? ) 4) Guest start report free pages: 4.1) Host may actively write StopCMD to the Host2Guest register before the guest finishes; or 4.2) Guest finishes reporting, write StopCMD the Guest2HOST register, which traps to QEMU, to stop. Best, Wei

...something else that works. > Thanks for the suggestion. Probably I haven't fully understood it. Please see the example below: 1) host-to-guest ctrl_vq: StartCMD, ID=1 2) guest-to-host free_page_vq: free_page, ID=1 free_page, ID=1 free_page, ID=1 free_page, ID=1 3) host-to-guest ctrl_vq: StopCMD, ID=1 4) initiate the 2nd try of live migration via host-to-guest ctrl_vq: StartCMD, ID=2 5) the guest-to-host free_page_vq might look like this: free_page, ID=1 free_page, ID=1 free_page, ID=2 free_page, ID=2 The device will need to drop (pop out the two entries and push them back) the first 2...

...ds the Host2Guest >> register, and detaches all the used buffers from free_page_vq; >> (then for each StartCMD, the free_page_vq will always have no obsolete free >> page hints, right? ) >> >> 4) Guest start report free pages: >> 4.1) Host may actively write StopCMD to the Host2Guest register before >> the guest finishes; or >> 4.2) Guest finishes reporting, write StopCMD the Guest2HOST register, >> which traps to QEMU, to stop. >> >> >> Best, >> Wei > I am not sure it matters whether a VQ or the config are us...

On Sat, Sep 30, 2017 at 12:05:54PM +0800, Wei Wang wrote: > Add a new vq, ctrl_vq, to handle commands between the host and guest. > With this feature, we will be able to have the control plane and data > plane separated. In other words, the control related commands of each > feature will be sent via the ctrl_vq, meanwhile each feature may have > its own vq used as a data plane. >

On Sat, Sep 30, 2017 at 12:05:54PM +0800, Wei Wang wrote: > Add a new vq, ctrl_vq, to handle commands between the host and guest. > With this feature, we will be able to have the control plane and data > plane separated. In other words, the control related commands of each > feature will be sent via the ctrl_vq, meanwhile each feature may have > its own vq used as a data plane. >