From: Steven Rostedt <rostedt@goodmis.org>
To: Vineet Gupta <vineet.gupta@linux.dev>
Cc: mhiramat@kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com, andrii@kernel.org,
peterz@infradead.org, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH 2/2] tracing: fgraph: Add a cond_resched() to the shadow stack retry loop
Date: Wed, 23 Sep 2026 04:47:30 -0400 [thread overview]
Message-ID: <20260923044730.1bc0a81c@fedora> (raw)
In-Reply-To: <20260922225526.1554758-3-vineet.gupta@linux.dev>
On Tue, 22 Sep 2026 15:55:26 -0700
Vineet Gupta <vineet.gupta@linux.dev> wrote:
> This is supplementary to previous patch and is effective only for
> !PREEMPTION kernels.
FYI, a patch in a series should never mention "the previous patch" as
if it gets committed, order in git history is not easily seen. Thus, a
change log should mention the added functionality itself and not a
patch sent to the mailing list.
But that said, this patch is likely not going to be added because
!PREEMPTION is being deprecated specifically to get rid of
cond_rescheds. Hence, I'm not adding any new ones.
-- Steve
next prev parent reply other threads:[~2026-09-23 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 22:55 [PATCH 0/2] tracing: fgraph: cut the cost of the shadow stack retry loop Vineet Gupta
2026-09-22 22:55 ` [PATCH 1/2] tracing: fgraph: Raise FTRACE_RETSTACK_ALLOC_SIZE to 1024 Vineet Gupta
2026-09-24 10:00 ` Peter Zijlstra
2026-09-25 19:32 ` Vineet Gupta
2026-09-26 12:46 ` Steven Rostedt
2026-09-22 22:55 ` [PATCH 2/2] tracing: fgraph: Add a cond_resched() to the shadow stack retry loop Vineet Gupta
2026-09-23 8:47 ` Steven Rostedt [this message]
2026-09-24 20:45 ` [PATCH 0/2] tracing: fgraph: cut the cost of " Steven Rostedt
2026-09-25 2:31 ` Vineet Gupta
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=20260923044730.1bc0a81c@fedora \
--to=rostedt@goodmis.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=vineet.gupta@linux.dev \
/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.