Re: [MirageOS-devel] NTP client integration with MirageOS / Mini-OS

[Hannes Mehnert <hannes@xxxxxxxxxxx>]

On 08/09/2016 11:28, Thomas Leonard wrote:
> On 7 September 2016 at 15:26, Hannes Mehnert <hannes@xxxxxxxxxxx> wrote:
>> On 22/08/2016 15:16, Thomas Leonard wrote:
> 
> [ running a test clock at a multiple of the real clock's speed ]
> 
>>> Right, but this is a hack because we don't have internal state. It
>>> runs slower that it could (it's still waiting, just for less time) and
>>> may fail due to timeouts if the real system is under load (or just
>>> slow). With state, the clock could be set to whatever the unit-tests
>>> want the time to be, allowing the tests to run at the full speed of
>>> the CPU and without the behaviour depending on the load.
>>
>> I cannot follow, need to see code.
> 
> I've made a simpler version of the CueKeeper test code I posted earlier:
> 
>   https://github.com/talex5/mirage-clock-test

Interesting, thanks!  But this still uses the old MirageOS API (<=V2),
and includes lots of mutable state.

That somehow indicates that even with the earlier API you can do the
testing you want (without callouts to Unix.sleep/Lwt_unix.sleep)!?
Which makes me even more confused, since I understood your argument
above that this is not possible!?


hannes

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel