Hi Biju, On Wed, Oct 10, 2018 at 11:50 AM Biju Das <biju.das@xxxxxxxxxxxxxx> wrote: > > > Note:- > > > > > > For R-Car M3-W board, inconsistency-check and nanosleep tests are > > working fine. > > > > > > However there is a failure with clocksource_switch "asynchronous" test. > > > The inconsistency-check is failing for "arch_sys_counter" after some > > > clocksource_switch operations > > > > > > So I skipped the "clocksource_switching" for arch_sys_counter and > > > the asynchronous test is passing for > > > CMT0/1/2/3 timers. > > > > Sorry, being no timer expert, I don't understand the impact of the above > > paragraph. > > We may start a discussion on this, when we start upstreaming CMT for R-Car M3-W devices. > > Basically clocksource_switch test in "selftests "uses 2 threads, > In 1 thread it executes inconsistency-check test followed by nano sleep test > and on the second thread it keep changing clock source one after the another. > > This test always fails on R-Car M3-W which is based on arm64. Sergei already enabled CMT on R-Car V3M and V3H, perhaps he has seen similar issues? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds