On Thu, 20 Jun 2013, David Vrabel wrote:
> From: David Vrabel <david.vra...@citrix.com>
>
> The high resolution timer code gets notified of step changes to the
> system time with clock_was_set() or clock_was_set_delayed() calls. If
> other parts of the kernel require similar notification there is no
> clear place to hook into.
You fail to explain why any other part of the kernel requires a
notification.
We went great length to confine timekeeping inside the core code and
now you add random notifiers along with totally ugly tasklet
constructs. What for?
Without a reasonable explanation of the problem you are trying to
solve this is going nowhere near the tree.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
