From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.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>,
Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
linux-hardening@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v2 1/2] tracing: ring-buffer: Have the ring buffer code do the vmap of physical memory
Date: Mon, 31 Mar 2025 21:36:16 -0400 [thread overview]
Message-ID: <20250331213616.18ccfa37@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=wh4b8hNT5XRDj9M4damUmij2bJGaRamqQ_icEkVUv8svg@mail.gmail.com>
On Mon, 31 Mar 2025 17:49:07 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> For example, just adding flush_dcache_range() into
> include/asm-generic/cacheflush.h should be more-or-less trivial, with
> the same kinds of "architectures can make clear they have their own
> optimized version".
Just so I'm clear. Are you suggesting to add flush_dcache_range() to
cacheflush.h and using that?
Looks like some of the code would be able to remove the ifdefs:
#ifdef CONFIG_PPC
flush_dcache_range(...);
#endif
if that's the case.
-- Steve
next prev parent reply other threads:[~2025-04-01 1:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 14:34 [PATCH v2 0/2] ring-buffer: Allow persistent memory to be user space mmapped Steven Rostedt
2025-03-31 14:34 ` [PATCH v2 1/2] tracing: ring-buffer: Have the ring buffer code do the vmap of physical memory Steven Rostedt
2025-03-31 16:55 ` Linus Torvalds
2025-03-31 17:39 ` Steven Rostedt
2025-03-31 19:12 ` Linus Torvalds
2025-03-31 20:58 ` Steven Rostedt
2025-03-31 21:42 ` Linus Torvalds
2025-03-31 23:42 ` Steven Rostedt
2025-04-01 0:09 ` Jann Horn
2025-04-01 1:02 ` Steven Rostedt
2025-04-01 1:28 ` Jann Horn
2025-04-01 1:50 ` Steven Rostedt
2025-04-01 2:23 ` Mathieu Desnoyers
2025-04-01 1:30 ` Linus Torvalds
2025-04-01 1:41 ` Steven Rostedt
2025-04-01 1:55 ` Linus Torvalds
2025-04-01 9:53 ` Ingo Molnar
2025-04-01 0:11 ` Linus Torvalds
2025-04-01 0:27 ` Linus Torvalds
2025-04-01 0:30 ` Steven Rostedt
2025-04-01 0:38 ` Linus Torvalds
2025-04-01 0:49 ` Linus Torvalds
2025-04-01 1:36 ` Steven Rostedt [this message]
2025-04-01 1:44 ` Linus Torvalds
2025-04-03 5:59 ` Herbert Xu
2025-04-03 16:47 ` Linus Torvalds
2025-04-01 9:56 ` Mike Rapoport
2025-04-01 15:11 ` Steven Rostedt
2025-04-01 15:26 ` Mike Rapoport
2025-04-01 15:54 ` Steven Rostedt
2025-04-01 17:58 ` Mike Rapoport
2025-04-03 16:45 ` Kees Cook
2025-04-03 16:51 ` Linus Torvalds
2025-04-03 17:15 ` Steven Rostedt
2025-03-31 14:34 ` [PATCH v2 2/2] ring-buffer: Allow 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=20250331213616.18ccfa37@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--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=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=vdonnefort@google.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).