On Mon, Dec 21, 2020 at 7:44 AM Michael Ellerman <m...@ellerman.id.au> wrote:
> Andy Shevchenko <andy.shevche...@gmail.com> writes:
> > On Fri, Dec 18, 2020 at 4:37 PM Enrico Weigelt, metux IT consult
> > <i...@metux.net> wrote:
> >
> >> + if (printk_ratelimit())
> >> + pr_warn("spurious IRQ: irq=%d hwirq=%d
> >> nr_irqs=%d\n",
> >> + irq, hwirq, nr_irqs);
> >
> > Perhaps you missed pr_warn_ratelimit() macro which is already in the
> > kernel for a long time.
>
> pr_warn_ratelimited() which calls printk_ratelimited().
I stand corrected.
Right, that's what I had in mind (actually didn't know that there are variants).
Thanks!
> And see the comment above printk_ratelimit():
>
> /*
> * Please don't use printk_ratelimit(), because it shares ratelimiting state
> * with all other unrelated printk_ratelimit() callsites. Instead use
> * printk_ratelimited() or plain old __ratelimit().
> */
--
With Best Regards,
Andy Shevchenko
