[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h76vepzp.ffs@tglx>
Date: Thu, 14 Apr 2022 15:47:22 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Zqiang <qiang1.zhang@...el.com>, akpm@...ux-foundation.org,
peterz@...radead.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] irq_work: Add event-tracing points for irq_work
On Thu, Apr 14 2022 at 14:38, Zqiang wrote:
> +#define CREATE_TRACE_POINTS
> +#include <trace/events/irq_work.h>
> +
> static DEFINE_PER_CPU(struct llist_head, raised_list);
> static DEFINE_PER_CPU(struct llist_head, lazy_list);
> static DEFINE_PER_CPU(struct task_struct *, irq_workd);
> @@ -81,7 +84,9 @@ static void __irq_work_queue_local(struct irq_work *work)
> bool rt_lazy_work = false;
> bool lazy_work = false;
> int work_flags;
> + int cpu = smp_processor_id();
>
> + trace_irq_work_queue_on(cpu, work);
What about work_flags to see on which list this ends up?
Thanks,
tglx
Powered by blists - more mailing lists