From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] arm64: fix flush_cache_range
Date: Wed, 25 May 2016 18:27:07 +0100 [thread overview]
Message-ID: <20160525172705.GD19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160525152255.GH5996@e104818-lin.cambridge.arm.com>
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.
next prev parent reply other threads:[~2016-05-25 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 11:16 [PATCH 1/1] arm64: fix flush_cache_range Zhen Lei
2016-05-24 11:37 ` Mark Rutland
2016-05-24 12:19 ` Leizhen (ThunderTown)
2016-05-24 13:02 ` Catalin Marinas
[not found] ` <5744FDD0.8060504@huawei.com>
2016-05-25 3:36 ` Leizhen (ThunderTown)
2016-05-25 10:50 ` Catalin Marinas
2016-05-26 3:40 ` Leizhen (ThunderTown)
2016-05-26 11:46 ` Leizhen (ThunderTown)
2016-05-26 12:04 ` Russell King - ARM Linux
2016-05-26 16:36 ` Catalin Marinas
2016-05-24 15:12 ` Mark Rutland
2016-05-25 15:22 ` Catalin Marinas
2016-05-25 17:27 ` Russell King - ARM Linux [this message]
2016-05-26 16:44 ` Catalin Marinas
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=20160525172705.GD19428@n2100.arm.linux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.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).