Re: is printk() safe within a timekeeper_seq write section?
On Tue, Mar 11, 2014 at 12:29:45PM -0700, John Stultz wrote: > So I don't think I've seen anything like the above in my testing, but it > may just be very hard to get that path to trigger.
You have to explicitly enable HRTICK for this to be possible; its disabled by default.