[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YvydlP+XivIwfAPO@worktop.programming.kicks-ass.net>
Date: Wed, 17 Aug 2022 09:49:40 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Davidlohr Bueso <dave@...olabs.net>,
Mark Rutland <mark.rutland@....com>,
Dave Jiang <dave.jiang@...el.com>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
linux-cxl@...r.kernel.org, nvdimm@...ts.linux.dev,
bwidawsk@...nel.org, ira.weiny@...el.com, vishal.l.verma@...el.com,
alison.schofield@...el.com, a.manzanares@...sung.com,
linux-arch@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
linux-arm-kernel@...ts.infradead.org, bp@...en8.de, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arch/cacheflush: Introduce flush_all_caches()
On Tue, Aug 16, 2022 at 10:42:03AM -0700, Dan Williams wrote:
> I also think this cache_flush_region() API wants a prominent comment
> clarifying the limited applicability of this API. I.e. that it is not
> for general purpose usage, not for VMs, and only for select bare metal
> scenarios that instantaneously invalidate wide swaths of memory.
> Otherwise, I can now see how this looks like a potentially scary
> expansion of the usage of wbinvd.
This; because adding a generic API like this makes it ripe for usage.
And this is absolutely the very last thing we want used.
Powered by blists - more mailing lists