[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiKgKBeNBVFin4XYXLNSNDPnL1kdidigV6qfQ+6tY8cHA@mail.gmail.com>
Date: Mon, 31 Mar 2025 18:44:40 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Steven Rostedt <rostedt@...dmis.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 at 18:35, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> Just so I'm clear. Are you suggesting to add flush_dcache_range() to
> cacheflush.h and using that?
No, let's wait for it to be actually considered a problem.
And I think Jann is right that for kernel ranges you should use
flush_kernel_vmap_range() anyway.
Oh how I hate incoherent data caches.
Linus
Powered by blists - more mailing lists