Re: [PATCH v1] Revert "clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock"

2017-03-11 Thread Daniel Lezcano
On Thu, Mar 09, 2017 at 05:58:38PM +0100, Romain Izard wrote: > This reverts commit 7b9f1d16e6d1 ("clocksource/drivers/tcb_clksrc: Use > 32 bit tcb as sched_clock"). In the current state, the kernel warns > against a late registration of the new sched_clock, the printk clock > resets after only a

Re: [PATCH v1] Revert "clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock"

2017-03-11 Thread Daniel Lezcano
On Thu, Mar 09, 2017 at 05:58:38PM +0100, Romain Izard wrote: > This reverts commit 7b9f1d16e6d1 ("clocksource/drivers/tcb_clksrc: Use > 32 bit tcb as sched_clock"). In the current state, the kernel warns > against a late registration of the new sched_clock, the printk clock > resets after only a

[PATCH v1] Revert "clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock"

2017-03-09 Thread Romain Izard
This reverts commit 7b9f1d16e6d1 ("clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock"). In the current state, the kernel warns against a late registration of the new sched_clock, the printk clock resets after only a few minutes, and it seems that scheduling can be affected as well.

[PATCH v1] Revert "clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock"

2017-03-09 Thread Romain Izard
This reverts commit 7b9f1d16e6d1 ("clocksource/drivers/tcb_clksrc: Use 32 bit tcb as sched_clock"). In the current state, the kernel warns against a late registration of the new sched_clock, the printk clock resets after only a few minutes, and it seems that scheduling can be affected as well.