Re: [PATCH 21/21] time: Rework debugging variables so they aren't global

Ingo Molnar
2015-04-02T07:51:58Z

* Peter Zijlstra <peterz@infradead.org> wrote:

> On Wed, Apr 01, 2015 at 08:34:41PM -0700, John Stultz wrote:
> > Ingo suggested that the timekeeping debugging variables
> > recently added should not be global, and should be tied
> > to the timekeeper's read_base.
>
> But why? its the same hardware clock for both tkr's. Surely if one goes
> funny the other will too.
>
> It doesn't make sense to duplicate this.

Well, could it be moved to the timekeeper data structure? What I was
opposed to was making it super-global, after all the (nice) effort we
made to tidy up global data structures in this area.

Thanks,

Ingo