On 06/06/19 17:14, Sean Christopherson wrote: > The code disagrees, e.g. > > /* > * Are we running in atomic context? WARNING: this macro cannot > * always detect atomic context; in particular, it cannot know about > * held spinlocks in non-preemptible kernels. Thus it should not be > * used in the general case to determine whether sleeping is possible. > * Do not use in_atomic() in driver code. > */ > #define in_atomic() (preempt_count() != 0) You're totally right. "_irqoff" seems to be the common suffix for irq-disabled functions. Paolo
