From: Steven Rostedt <rostedt@goodmis.org>
To: Usama Arif <usama.arif@linux.dev>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
leitao@debian.org
Subject: Re: [RFC] tracing: Try user copies with page faults disabled first
Date: Tue, 21 Jul 2026 17:05:09 -0400 [thread overview]
Message-ID: <20260721170509.3d372897@gandalf.local.home> (raw)
In-Reply-To: <20260717173758.3644427-1-usama.arif@linux.dev>
On Fri, 17 Jul 2026 10:37:57 -0700
Usama Arif <usama.arif@linux.dev> wrote:
> I think the actual problem might be:
> https://lore.kernel.org/all/20260717173252.3431565-1-usama.arif@linux.dev/
Ah probably. Thanks for finding and fixing it. I'll add that one to my
queue and set this patch to "superseded".
-- Steve
prev parent reply other threads:[~2026-07-21 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 15:54 [RFC] tracing: Try user copies with page faults disabled first Usama Arif
2026-07-15 19:11 ` Steven Rostedt
2026-07-16 12:05 ` Usama Arif
2026-07-17 17:37 ` Usama Arif
2026-07-21 21:05 ` Steven Rostedt [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=20260721170509.3d372897@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=usama.arif@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox