From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vincent Donnefort <vdonnefort@google.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Jann Horn <jannh@google.com>
Subject: Re: [PATCH v6 0/4] tracing: Clean up persistent ring buffer code
Date: Wed, 2 Apr 2025 12:00:03 -0400 [thread overview]
Message-ID: <24fcfce6-6ec9-46e4-bcd6-307814fcea5c@efficios.com> (raw)
In-Reply-To: <20250402114923.132217c1@gandalf.local.home>
On 2025-04-02 11:49, Steven Rostedt wrote:
> On Wed, 2 Apr 2025 10:56:51 -0400
> Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
[...]
>> Please let me know if I'm missing something,
>
> I guess what you are missing is that the code no longer is aimed at having
> vmap_page_range() ever get mapped to user space ;-)
Thanks for the clarification!
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2025-04-02 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 14:49 Steven Rostedt
2025-04-02 14:49 ` [PATCH v6 1/4] tracing: Enforce the persistent ring buffer to be page aligned Steven Rostedt
2025-04-02 14:49 ` [PATCH v6 2/4] tracing: Have reserve_mem use phys_to_virt() and separate from memmap buffer Steven Rostedt
2025-04-02 14:49 ` [PATCH v6 3/4] tracing: Use vmap_page_range() to map memmap ring buffer Steven Rostedt
2025-04-06 17:39 ` Guenter Roeck
2025-04-07 15:23 ` Steven Rostedt
2025-04-07 15:57 ` Guenter Roeck
2025-04-02 14:49 ` [PATCH v6 4/4] ring-buffer: Use flush_kernel_vmap_range() over flush_dcache_folio() Steven Rostedt
2025-04-02 14:56 ` [PATCH v6 0/4] tracing: Clean up persistent ring buffer code Mathieu Desnoyers
2025-04-02 15:49 ` Steven Rostedt
2025-04-02 16:00 ` Mathieu Desnoyers [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=24fcfce6-6ec9-46e4-bcd6-307814fcea5c@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=vdonnefort@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®