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 2/3] tracing: Record task flag NEED_RESCHED_LAZY.
Date: Tue, 22 Oct 2024 03:18:27 -0400 [thread overview]
Message-ID: <20241022031827.21e70b2b@rorschach.local.home> (raw)
In-Reply-To: <20241021151257.102296-3-bigeasy@linutronix.de>
On Mon, 21 Oct 2024 17:08:41 +0200
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> enum trace_flag_type {
> TRACE_FLAG_IRQS_OFF = 0x01,
> TRACE_FLAG_NEED_RESCHED = 0x02,
> + TRACE_FLAG_NEED_RESCHED_LAZY = 0x04,
> TRACE_FLAG_HARDIRQ = 0x08,
> TRACE_FLAG_SOFTIRQ = 0x10,
> TRACE_FLAG_PREEMPT_RESCHED = 0x20,
As I stated in the other email, these are user visible. Should probably
make the LAZY flag 0x100, as the trace_flags are 16 bits worth.
-- Steve
next prev parent reply other threads:[~2024-10-22 7:18 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
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 [this message]
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=20241022031827.21e70b2b@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.