Re: [PATCH v2 05/15] ia64: convert to legacy_timer_tick

2020-12-18 Thread John Paul Adrian Glaubitz
Hi Arnd! On 12/18/20 11:13 PM, John Paul Adrian Glaubitz wrote: >> I've attached a patch for a partial revert of my original change, this >> should still work with the final cleanup on top, but restore the loop >> plus the local_irq_enable()/local_irq_disable() that I dropped from >> the original

Re: [PATCH v2 05/15] ia64: convert to legacy_timer_tick

2020-12-18 Thread John Paul Adrian Glaubitz
Hi Arnd! On 12/18/20 11:07 PM, Arnd Bergmann wrote: > Sorry for causing this bug, and thank you for bisecting it > down to my patch. > > Do you see any other strange behavior with that patch, or is > this the only symptom you are aware of? This seems to be the only issue I'm seeing so far.

Re: [PATCH v2 05/15] ia64: convert to legacy_timer_tick

2020-12-18 Thread Arnd Bergmann
On Fri, Dec 18, 2020 at 10:29 PM John Paul Adrian Glaubitz wrote: > > Hi Arnd! > > On 10/30/20 4:17 PM, Arnd Bergmann wrote: > > ia64 is the only architecture that calls xtime_update() in a loop, > > once for each jiffie that has passed since the last event. > > > > Before commit 3171a0305d62

Re: [PATCH v2 05/15] ia64: convert to legacy_timer_tick

2020-12-18 Thread John Paul Adrian Glaubitz
Hi Arnd! On 10/30/20 4:17 PM, Arnd Bergmann wrote: > ia64 is the only architecture that calls xtime_update() in a loop, > once for each jiffie that has passed since the last event. > > Before commit 3171a0305d62 ("[PATCH] simplify update_times (avoid > jiffies/jiffies_64 aliasing problem)") in

[PATCH v2 05/15] ia64: convert to legacy_timer_tick

2020-10-30 Thread Arnd Bergmann
From: Arnd Bergmann ia64 is the only architecture that calls xtime_update() in a loop, once for each jiffie that has passed since the last event. Before commit 3171a0305d62 ("[PATCH] simplify update_times (avoid jiffies/jiffies_64 aliasing problem)") in 2006, it could not actually do this any