From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.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 v3 3/5] tracing: Use vmap_page_range() to map memmap ring buffer
Date: Tue, 1 Apr 2025 17:41:55 -0400 [thread overview]
Message-ID: <20250401174156.4e9d3b23@gandalf.local.home> (raw)
In-Reply-To: <20250401203331.901028151@goodmis.org>
On Tue, 01 Apr 2025 16:25:52 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> -static u64 map_pages(u64 start, u64 size)
> +static u64 map_pages(unsigned long start, unsigned long size)
> {
> - struct page **pages;
> - phys_addr_t page_start;
> - unsigned int page_count;
> - unsigned int i;
> - void *vaddr;
> + unsigned long vmap_start, vmap_end;
Bah, looks like I have whitespace issues. Will send an update to fix this
and the change log for patch 4.
> + struct vm_struct *area;
> + int ret;
>
next prev parent reply other threads:[~2025-04-01 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 20:25 [PATCH v3 0/5] ring-buffer: Allow persistent memory to be user space mmapped Steven Rostedt
2025-04-01 20:25 ` [PATCH v3 1/5] tracing: Enforce the persistent ring buffer to be page aligned Steven Rostedt
2025-04-01 20:25 ` [PATCH v3 2/5] tracing: Have reserve_mem use phys_to_virt() and separate from memmap buffer Steven Rostedt
2025-04-01 20:25 ` [PATCH v3 3/5] tracing: Use vmap_page_range() to map memmap ring buffer Steven Rostedt
2025-04-01 21:41 ` Steven Rostedt [this message]
2025-04-01 20:25 ` [PATCH v3 4/5] ring-buffer: Use flush_kernel_vmap_range() over flush_dcache_folio() Steven Rostedt
2025-04-01 20:39 ` Steven Rostedt
2025-04-01 20:25 ` [PATCH v3 5/5] ring-buffer: Allow reserve_mem persistent ring buffers to be mmapped 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=20250401174156.4e9d3b23@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.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 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.