[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250331213616.18ccfa37@gandalf.local.home>
Date: Mon, 31 Mar 2025 21:36:16 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Masami
Hiramatsu <mhiramat@...nel.org>, Mark Rutland <mark.rutland@....com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>, Vincent Donnefort <vdonnefort@...gle.com>,
Vlastimil Babka <vbabka@...e.cz>, Mike Rapoport <rppt@...nel.org>, Kees
Cook <kees@...nel.org>, Tony Luck <tony.luck@...el.com>, "Guilherme G.
Piccoli" <gpiccoli@...lia.com>, linux-hardening@...r.kernel.org, Matthew
Wilcox <willy@...radead.org>
Subject: Re: [PATCH v2 1/2] tracing: ring-buffer: Have the ring buffer code
do the vmap of physical memory
On Mon, 31 Mar 2025 17:49:07 -0700
Linus Torvalds <torvalds@...ux-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
Powered by blists - more mailing lists