> > The usage is to construct a secondary hot standby VM (SVM), identical with
> the primary VM (PVM).
> > When an virtual DMA happens in PVM side, we need to know at which
> instruction boundary the virtual DMA is delivered, so that we can replay the
> virtual DMA event at the 2nd VM side, to keep
On Fri, Nov 25, 2016 at 09:17:08AM +, Dong, Eddie wrote:
> > On Thu, Nov 24, 2016 at 08:44:06AM +, Dong, Eddie wrote:
> > > Under certain situation, we have a requirement to apply the
> > virtual DMA event in a deterministic way. Current Qemu uses asynchronous
> > approach to emula
>
> On Thu, Nov 24, 2016 at 08:44:06AM +, Dong, Eddie wrote:
> > Under certain situation, we have a requirement to apply the
> virtual DMA event in a deterministic way. Current Qemu uses asynchronous
> approach to emulate the virtual IO events since quite long time ago. I am
> wonderi
On Thu, Nov 24, 2016 at 08:44:06AM +, Dong, Eddie wrote:
> Under certain situation, we have a requirement to apply the virtual
> DMA event in a deterministic way. Current Qemu uses asynchronous approach to
> emulate the virtual IO events since quite long time ago. I am wondering if w
Hi:
Under certain situation, we have a requirement to apply the virtual
DMA event in a deterministic way. Current Qemu uses asynchronous approach to
emulate the virtual IO events since quite long time ago. I am wondering if we
still have an option to choose the synchronous emulation sol
