From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org,
Indu Bhagat <indu.bhagat@oracle.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, Mark Brown <broonie@kernel.org>,
linux-toolchains@vger.kernel.org, Jordan Rome <jordalgo@meta.com>,
Sam James <sam@gentoo.org>,
linux-trace-kernel@vger.kernel.org,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Jens Remus <jremus@linux.ibm.com>,
Florian Weimer <fweimer@redhat.com>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH v3 11/19] unwind: Add deferred user space unwinding API
Date: Wed, 30 Oct 2024 11:25:07 -0700 [thread overview]
Message-ID: <20241030182507.wpjdsvnitn7k2q2p@treble.attlocal.net> (raw)
In-Reply-To: <20241030174752.gwzk6q6n2f3sg52a@treble.attlocal.net>
On Wed, Oct 30, 2024 at 10:47:55AM -0700, Josh Poimboeuf wrote:
> On Wed, Oct 30, 2024 at 09:44:14AM -0400, Mathieu Desnoyers wrote:
> > What you want here is to move the point where you clear the task
> > cookie to _after_ completion of stack unwind. There are a few ways
> > this can be done:
> >
> > A) Clear the task cookie in the task_work() right after the
> > unwind_user_deferred() is completed. Downside: if some long task work
> > happen to be done after the stack walk, a new unwind_user_deferred()
> > could be issued again and we may end up looping forever taking stack
> > unwind and never actually making forward progress.
> >
> > B) Clear the task cookie after the exit_to_user_mode_loop is done,
> > before returning to user-space, while interrupts are disabled.
>
> Problem is, if another tracer calls unwind_user_deferred() for the first
> time, after the task work but before the task cookie gets cleared, it
> will see the cookie is non-zero and will fail to schedule another task
> work. So its callback never gets called.
How about we:
- clear task cookie on entry or exit from user space
- use a different variable (rather than clearing of task cookie) to
communicate whether task work is pending
- keep track of which callbacks have been called for this cookie
something like so?
int unwind_user_deferred(struct unwind_callback *callback, u64 *ctx_cookie, void *data)
{
struct unwind_task_info *info = ¤t->unwind_task_info;
unsigned int work_pending = work_pending;
u64 cookie = info->ctx_cookie;
int idx = callback->idx;
if (WARN_ON_ONCE(in_nmi()))
return -EINVAL;
if (!current->mm)
return -EINVAL;
guard(irqsave)();
if (cookie && (info->pending_callbacks & (1 << idx))) {
/* callback already scheduled */
goto done;
}
/*
* If this is the first call from any caller since the most recent
* entry from user space, initialize the task context cookie.
*/
if (!cookie) {
u64 cpu = raw_smp_processor_id();
u64 ctx_ctr;
__this_cpu_inc(unwind_ctx_ctr);
ctx_ctr = __this_cpu_read(unwind_ctx_ctr);
cookie = ctx_to_cookie(cpu, ctx_ctr);
info->ctx_cookie = cookie;
} else {
if (cookie == info->last_cookies[idx]) {
/*
* The callback has already been called with this unwind,
* nothing to do.
*/
goto done;
}
if (info->pending_callbacks & (1 << idx)) {
/* callback already scheduled */
goto done;
}
}
info->pending_callbacks |= (1 << idx);
info->privs[idx] = data;
info->last_cookies[idx] = cookie;
if (!info->task_pending) {
info->task_pending = 1; /* cleared by unwind_user_task_work() */
task_work_add(current, &info->work, TWA_RESUME);
}
done:
if (ctx_cookie)
*ctx_cookie = cookie;
return 0;
}
--
Josh
next prev parent reply other threads:[~2024-10-30 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1730150953.git.jpoimboe@kernel.org>
[not found] ` <a94eb70a80c4a13dedb2655b7848304a992cb1b0.1730150953.git.jpoimboe@kernel.org>
[not found] ` <20241029135617.GB14555@noisy.programming.kicks-ass.net>
[not found] ` <20241029171752.4y67p3ob24riogpi@treble.attlocal.net>
[not found] ` <bcd11a07-45fb-442b-a25b-5cadc6aac0e6@efficios.com>
[not found] ` <20241029183440.fbwoistveyxneezt@treble.attlocal.net>
2024-10-30 13:44 ` [PATCH v3 11/19] unwind: Add deferred user space unwinding API Mathieu Desnoyers
2024-10-30 17:47 ` Josh Poimboeuf
2024-10-30 17:55 ` Josh Poimboeuf
2024-10-30 18:25 ` Josh Poimboeuf [this message]
[not found] ` <42c0a99236af65c09c8182e260af7bcf5aa1e158.1730150953.git.jpoimboe@kernel.org>
[not found] ` <20241105124053.523e93dd@gandalf.local.home>
2024-11-05 17:45 ` [PATCH v3 09/19] unwind: Introduce sframe user space unwinding Steven Rostedt
[not found] ` <1f83be89-b816-48a3-a7ee-9b72f07b558e@linux.ibm.com>
[not found] ` <20241113155040.6a9a1bed@gandalf.local.home>
[not found] ` <20241113211535.ghnw52wkgudkjvgv@jpoimboe>
[not found] ` <20241113171326.6d1ddc83@gandalf.local.home>
2024-11-13 22:21 ` Steven Rostedt
2024-11-13 22:25 ` Steven Rostedt
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=20241030182507.wpjdsvnitn7k2q2p@treble.attlocal.net \
--to=jpoimboe@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=broonie@kernel.org \
--cc=fweimer@redhat.com \
--cc=indu.bhagat@oracle.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=jordalgo@meta.com \
--cc=jremus@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sam@gentoo.org \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox