[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


On 27/07/2016 17:07, Mindy wrote:
> On 07/27/2016 02:05 PM, Matthew Gray wrote:
>> Should MCLOCK also implement the DEVICE signature? I think so, for
>> consistency.
> Making PCLOCK be a device looks completely reasonable to me, and I see
> no reason not to make MCLOCK be one as well.  Thoughts?

I can see value in making PCLOCK a device, but I fail to see any reason
to make MCLOCK a device.  I don't expect MCLOCK to have internal state,
neither to be able to error, nor that anyone would ever want to
disconnect from it.

For PCLOCK it makes sense since timezone and DST (plus adjustment to a
real clock) may be needed, but MCLOCK is some arbitrary, always
increasing, tick.  PCLOCK might then also need some adjust_t : t ->
offset -> unit function, or how do people expect the timezone to be set?

Or is there something I'm missing regarding MCLOCK?

Sorry to not have responded earlier here (and I can see that some amount
of implementation regarding this has already been done).


MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.