[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:12:30 +0100 |
On 18 July 2013 16:09, Frederic Konrad <address@hidden> wrote:
> On 18/07/2013 17:06, Peter Maydell wrote:
>>
>> 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.
>
>
> Yes, the documentation say that this command can give deterministic results
> that's why we asked.
As part of working through this it would be great if you could
write some developer documentation (in docs/ or possibly as a
comment somewhere sensible) that summarises how icount works,
what you need to do in a target-* to support it, etc.
[I suspect that by the time you're done you're going to be the
expert on icount...]
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, 2013/07/18
- 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