All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	tglx@linutronix.de, mingo@kernel.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
	ankur.a.arora@oracle.com, efault@gmx.de,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH v2 1/3] tracing: Replace TRACE_FLAG_IRQS_NOSUPPORT with its config option.
Date: Tue, 22 Oct 2024 03:14:18 -0400	[thread overview]
Message-ID: <20241022031418.12154e63@rorschach.local.home> (raw)
In-Reply-To: <20241021151257.102296-2-bigeasy@linutronix.de>

On Mon, 21 Oct 2024 17:08:40 +0200
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:

> From: Thomas Gleixner <tglx@linutronix.de>
> 
> The TRACE_FLAG_IRQS_NOSUPPORT flag is used by tracing_gen_ctx.*() to
> signal that CONFIG_TRACE_IRQFLAGS_SUPPORT is not enabled and tracing IRQ
> flags is not supported.
> 
> This could be replaced by using the 0 as flags and then deducting that
> there is no IRQFLAGS_SUPPORT based on the config option. The downside is
> that without CONFIG_TRACE_IRQFLAGS_SUPPORT we can not distinguish
> between no-IRQ passed flags and callers which passed 0. On the upside we
> have room for one additional flags which could be used for LAZY_PREEMPTION.
> 
> Remove TRACE_FLAG_IRQS_NOSUPPORT and set it flags are 0 and
> CONFIG_TRACE_IRQFLAGS_SUPPORT is not set.

We could also add that we have:

#
# Minimum requirements an architecture has to meet for us to
# be able to offer generic tracing facilities:
#
config TRACING_SUPPORT
        bool
        depends on TRACE_IRQFLAGS_SUPPORT
        depends on STACKTRACE_SUPPORT
        default y

So this can't even be built without TRACE_IRQFLAGS_SUPPORT!

> 
> [bigeasy: Commit descrption.]
> 
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
>  include/linux/trace_events.h |    7 +++----
>  kernel/trace/trace_output.c  |    2 +-
>  2 files changed, 4 insertions(+), 5 deletions(-)
> 
> --- a/include/linux/trace_events.h
> +++ b/include/linux/trace_events.h
> @@ -184,8 +184,7 @@ unsigned int tracing_gen_ctx_irq_test(un
>  
>  enum trace_flag_type {
>  	TRACE_FLAG_IRQS_OFF		= 0x01,
> -	TRACE_FLAG_IRQS_NOSUPPORT	= 0x02,
> -	TRACE_FLAG_NEED_RESCHED		= 0x04,
> +	TRACE_FLAG_NEED_RESCHED		= 0x02,

These flags are user visible (I probably should move them into uapi).
They are parsed by libtraceevent.

Please just remove NOSUPPORT and do not touch NEED_RESCHED.


>  	TRACE_FLAG_HARDIRQ		= 0x08,
>  	TRACE_FLAG_SOFTIRQ		= 0x10,
>  	TRACE_FLAG_PREEMPT_RESCHED	= 0x20,
> @@ -211,11 +210,11 @@ static inline unsigned int tracing_gen_c
>  
>  static inline unsigned int tracing_gen_ctx_flags(unsigned long irqflags)
>  {
> -	return tracing_gen_ctx_irq_test(TRACE_FLAG_IRQS_NOSUPPORT);
> +	return tracing_gen_ctx_irq_test(0);
>  }
>  static inline unsigned int tracing_gen_ctx(void)
>  {
> -	return tracing_gen_ctx_irq_test(TRACE_FLAG_IRQS_NOSUPPORT);
> +	return tracing_gen_ctx_irq_test(0);
>  }
>  #endif
>  
> --- a/kernel/trace/trace_output.c
> +++ b/kernel/trace/trace_output.c
> @@ -460,7 +460,7 @@ int trace_print_lat_fmt(struct trace_seq
>  		(entry->flags & TRACE_FLAG_IRQS_OFF && bh_off) ? 'D' :
>  		(entry->flags & TRACE_FLAG_IRQS_OFF) ? 'd' :
>  		bh_off ? 'b' :
> -		(entry->flags & TRACE_FLAG_IRQS_NOSUPPORT) ? 'X' :
> +		!IS_ENABLED(CONFIG_TRACE_IRQFLAGS_SUPPORT) ? 'X' :

Probably can even remove this check.

-- Steve

>  		'.';
>  
>  	switch (entry->flags & (TRACE_FLAG_NEED_RESCHED |


  reply	other threads:[~2024-10-22  7:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 15:08 [PATCH v2 0/3] Lazy preemption leftovers Sebastian Andrzej Siewior
2024-10-21 15:08 ` [PATCH v2 1/3] tracing: Replace TRACE_FLAG_IRQS_NOSUPPORT with its config option Sebastian Andrzej Siewior
2024-10-22  7:14   ` Steven Rostedt [this message]
2024-10-22  9:52     ` Sebastian Andrzej Siewior
2024-10-22 10:19       ` Steven Rostedt
2024-10-22 10:29         ` Sebastian Andrzej Siewior
2024-10-22 11:01     ` [PATCH] tracing: Remove TRACE_FLAG_IRQS_NOSUPPORT Sebastian Andrzej Siewior
2024-10-21 15:08 ` [PATCH v2 2/3] tracing: Record task flag NEED_RESCHED_LAZY Sebastian Andrzej Siewior
2024-10-22  7:18   ` Steven Rostedt
2024-10-22  7:26     ` Sebastian Andrzej Siewior
2024-10-21 15:08 ` [PATCH v2 3/3] riscv: add PREEMPT_LAZY support Sebastian Andrzej Siewior
2024-10-21 15:08   ` Sebastian Andrzej Siewior
2024-11-06 10:48   ` [tip: sched/core] " tip-bot2 for Jisheng Zhang
2024-12-11 22:32   ` [PATCH v2 3/3] " patchwork-bot+linux-riscv
2024-12-11 22:32     ` patchwork-bot+linux-riscv

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=20241022031418.12154e63@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=ankur.a.arora@oracle.com \
    --cc=bigeasy@linutronix.de \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=efault@gmx.de \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mgorman@suse.de \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    /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.