[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC 0/3] Determinitic behaviour with icount.
|
From: |
Peter Maydell |
|
Subject: |
Re: [Qemu-devel] [RFC 0/3] Determinitic behaviour with icount. |
|
Date: |
Thu, 18 Jul 2013 16:06:32 +0100 |
On 18 July 2013 16:02, <address@hidden> wrote:
> As I said in the last email, we have issues with determinism with icount.
> We are wondering if determinism is really ensured with icount?
My opinion is that it *should* be deterministic but it would
be unsurprising if the determinism had got broken along the way.
> Both icount and reverse execution need an instruction counter. icount use a
> count-down mechanism but reverse execution need a continuous counter. For now
> we have build a separate counter and we think that these two counters can be
> merged. However we would like feedback about this before modifying this.
I definitely think that there should only be one counter, not two.
thanks
-- PMM
- [Qemu-devel] [RFC 0/3] Determinitic behaviour with icount., fred . konrad, 2013/07/18
- [Qemu-devel] [RFC 2/3] icount: sync vm_clock on the next event., fred . konrad, 2013/07/18
- [Qemu-devel] [RFC 3/3] icount: create a new icount based timer., fred . konrad, 2013/07/18
- Re: [Qemu-devel] [RFC 0/3] Determinitic behaviour with icount.,
Peter Maydell <=
- Re: [Qemu-devel] [RFC 0/3] Determinitic behaviour with icount., Frederic Konrad, 2013/07/29
- Re: [Qemu-devel] [RFC 0/3] Determinitic behaviour with icount., Paolo Bonzini, 2013/07/29
- Re: [Qemu-devel] [RFC 0/3] Determinitic behaviour with icount., Frederic Konrad, 2013/07/30