Messages in this thread | | | Date | Fri, 21 Jun 2013 13:41:45 +0100 | From | David Vrabel <> | Subject | Re: [PATCH 2/4] time: add a notifier chain for when the system time is stepped |
| |
On 21/06/13 08:57, Thomas Gleixner wrote: > On Thu, 20 Jun 2013, David Vrabel wrote: > >> From: David Vrabel <david.vrabel@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.
This is needed by patch 3 in this series.
"The Xen wallclock is a software only clock within the Xen hypervisor that is used by: a) PV guests as the equivalent of a hardware RTC; and b) the hypervisor as the clock source for the emulated RTC provided to HVM guests.
Currently the Xen wallclock is only updated every 11 minutes if NTP is synchronized to its clock source. If a guest is started before NTP is synchronized it may see an incorrect wallclock time.
Use the clock_was_set notifier chain to receive a notification when the system time is stepped and update the wallclock to match the current system time."
> We went great length to confine timekeeping inside the core code and > now you add random notifiers along with totally ugly tasklet > constructs.
I'm not sure I understand your objection to the use of a tasklet. Using the hrtimer softirq for something that is no longer hrtimer-specific did not seem like the correct thing to do.
David
| |