On 2018-07-02 17:34:34 [+0800], gengdongjiu wrote: > The Linux kernel version is v4.1.46, and the preempt_rt patch is > patch-4.1.46-rt52.patch. the 4.1 series is no longer supported (neither RT wise nor non-RT, https://www.kernel.org/category/releases.html). I suggest to move away. If you notice this problem now it is hardly a long running project. > process will not be interrupt. But if the hrtimer is also runs in > process context the timer is useless when it's inaccurate. so I want to > consult you whether this is expected behavior? whether is reasonable to move the timer IRQ > handling to a thread? This depends on your expectations. The timer is defined not to fire before the programmed time. So it fires as soon as possible _after_ the programmed time. > I think this is why hrtimer is run as a thread, I tried to set > hrtimer.irqsafe to 1, but the timer still seemed not right. Could anyone > give some advise? Thanks. By setting irqsafe to 1 you ensure taht the timer will fire from the timer interrupt and before doing so you should ensure that the timer is indeed IRQ safe. Depending on what you do it is possible that the timer fires early but the application notices it later (the scheduler will first handle RT tasks according to their priorities followed by non RT tasks). Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
