All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Qiang1" <qiang1.zhang@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"peterz@infradead.org" <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] irq_work: Add event-tracing points for irq_work
Date: Fri, 15 Apr 2022 03:02:43 +0000	[thread overview]
Message-ID: <PH0PR11MB5880E763AADA0DB42865FFF4DAEE9@PH0PR11MB5880.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87h76vepzp.ffs@tglx>


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?

The tracepoint have been record 'work->node.a_flags'  through check it to sure 
this irq-wrok is queued on which list

Thanks
Zqiang

>Thanks,
>
>        tglx

      reply	other threads:[~2022-04-15  3:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  6:38 [PATCH] irq_work: Add event-tracing points for irq_work Zqiang
2022-04-14  9:32 ` Peter Zijlstra
2022-04-15  2:56   ` Zhang, Qiang1
2022-04-14 13:47 ` Thomas Gleixner
2022-04-15  3:02   ` Zhang, Qiang1 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PH0PR11MB5880E763AADA0DB42865FFF4DAEE9@PH0PR11MB5880.namprd11.prod.outlook.com \
    --to=qiang1.zhang@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.