We also started with a separate counter, but using icount, which is
intended to
provide just this functionality, is much more logical.
On 27/06/2014 13:17, Pavel Dovgaluk wrote:
On 27 June 2014 11:35, Pavel Dovgaluk wrote:
The major disadvantage of icount is that it's updated only on TB bou
On 27 June 2014 12:31, Pavel Dovgaluk wrote:
> I forgot about one more issue.
> When qemu stops execution on the breakpoint, the icount
> is decreased to the number of instructions in the block.
> But in this case the last instruction is not executed and
> should not affect the counter.
Yes, inde
> On 27 June 2014 11:35, Pavel Dovgaluk wrote:
> > The major disadvantage of icount is that it's updated only on TB boundaries.
> > When one instruction in the middle of the block uses virtual clock, it could
> > have different values for different divisions of the code to TB.
>
> This is only tr
> On 27 June 2014 11:35, Pavel Dovgaluk wrote:
> > The major disadvantage of icount is that it's updated only on TB boundaries.
> > When one instruction in the middle of the block uses virtual clock, it could
> > have different values for different divisions of the code to TB.
>
> This is only tr
On 27 June 2014 11:35, Pavel Dovgaluk wrote:
> The major disadvantage of icount is that it's updated only on TB boundaries.
> When one instruction in the middle of the block uses virtual clock, it could
> have different values for different divisions of the code to TB.
This is only true if the in
> -Original Message-
> From: Frederic Konrad [mailto:fred.kon...@greensocs.com]
> Sent: Friday, June 27, 2014 11:48 AM
> To: Pavel Dovgaluk
> Cc: Peter Crosthwaite; Paolo Bonzini; qemu-devel@nongnu.org Developers; Mark
> Burton
> Subject: Re: [Qemu-devel]
On 27 June 2014 06:18, Pavel Dovgaluk wrote:
> Our implementation is completely tested for qemu 1.5 and is in beta state for
> 2.0.50.
Note that you should post patches against current QEMU master;
patches against old releases like 1.5 are not something we could
use.
thanks
-- PMM
On 27/06/2014 08:11, Peter Crosthwaite wrote:
Hi Pavel,
On Fri, Jun 27, 2014 at 3:18 PM, Pavel Dovgaluk
wrote:
Hello!
We want to publish set of patches related to the reverse execution and
deterministic replay of qemu.
Our implementation of deterministic replay can be used for deterministic
> Subject: Re: [Qemu-devel] Reverse execution and deterministic replay
>
> Hi Pavel,
>
> On Fri, Jun 27, 2014 at 3:18 PM, Pavel Dovgaluk
> wrote:
> > Hello!
> >
> > We want to publish set of patches related to the reverse execution and
> > determin
Hi Pavel,
On Fri, Jun 27, 2014 at 3:18 PM, Pavel Dovgaluk
wrote:
> Hello!
>
> We want to publish set of patches related to the reverse execution and
> deterministic replay of qemu.
> Our implementation of deterministic replay can be used for deterministic and
> reverse debugging of
> guest code
Hello!
We want to publish set of patches related to the reverse execution and
deterministic replay of qemu.
Our implementation of deterministic replay can be used for deterministic and
reverse debugging of
guest code through gdb remote interface.
Execution recording writes non-deterministic eve
11 matches
Mail list logo
