[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160525172705.GD19428@n2100.arm.linux.org.uk>
Date: Wed, 25 May 2016 18:27:07 +0100
From: Russell King - ARM Linux <linux@...linux.org.uk>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Mark Rutland <mark.rutland@....com>,
"Leizhen (ThunderTown)" <thunder.leizhen@...wei.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Tianhong Ding <dingtianhong@...wei.com>,
Will Deacon <will.deacon@....com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Xinwei Hu <huxinwei@...wei.com>, Zefan Li <lizefan@...wei.com>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
Hanjun Guo <guohanjun@...wei.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/1] arm64: fix flush_cache_range
On Wed, May 25, 2016 at 04:22:55PM +0100, Catalin Marinas wrote:
> That's when we realised that the CoW problem no longer exists for
> non-aliasing VIPT caches. However, the I-cache counterpart 6060e8df5178
> has not been reverted.
I think I mostly agree, except for reverting 6060e8df5178, which I don't
think would be correct. That reintroduces the possibility of flushing
the I-cache twice in that path, once for aliasing vipt dcaches, and again
for asid tagged vivt icaches. I'd rather have the code structured so we
only do this once.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
Powered by blists - more mailing lists