On 08/19/2016 11:59 AM, Hannes Mehnert wrote:
On 19/08/2016 17:50, Hannes Mehnert wrote:
On 19/08/2016 17:04, Thomas Leonard wrote:
MCLOCK might have internal state for testing, although a global would
work there too if necessary.
I'm not sure I understand what you mean with "internal state for
testing" (and what your approach to testing there is - mine is mainly on
the purely implemented protocol rather than on the effectful layer).
to extend a bit: atm some testing in tcpip [0] uses a
fast_clock/fast_time, which are implementations of clock/time where the
clock ticks faster. the same approach can be used in the future. I
don't see how making mclock a device will help for testing.
I don't see how it helps now, but I don't have enough confidence in my
imagination to say there'll never be a situation where storing state
there is useful. It's a lot easier to say that `type t = unit`
privately and redefine that later, than to thread in a `t` where nothing
existed before.
-Mindy
_______________________________________________
MirageOS-devel mailing list
[email protected]
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
