From: ashoks@broadcom.com (Ashok Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] arm64: change PoC D-cache flush to PoU
Date: Tue, 15 Dec 2015 04:56:16 -0800 [thread overview]
Message-ID: <1450184178-28257-1-git-send-email-ashoks@broadcom.com> (raw)
For keeping I and D coherent, dcache flush till PoU(Point of Unification)
should be sufficient instead of doing till PoC(Point of coherence).
In SoC with more levels of cache, there could be a performance hit in doing
flush till PoC as __flush_dcache_area does both flush and invalidate.
Introduced new API __clean_dcache_area_pou which does only clean till PoU.
Also deferred dcache flush in __cpu_copy_user_page to __sync_icache_dcache.
changes since v1 [1]:
Incorporated Mark Rutland's review comments of
* renaming __flush_dcache_area_pou to __clean_dcache_area_pou
* using inner shareable domain for dsb in __clean_dcache_area_pou
* having a common macro for __flush_dcache_area and
__clean_dcache_area_pou.
Thanks,
Ashok
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-December/393527.html
Ashok Kumar (2):
arm64: Defer dcache flush in __cpu_copy_user_page
arm64: Use PoU cache instr for I/D coherency
arch/arm64/include/asm/cacheflush.h | 1 +
arch/arm64/mm/cache.S | 47 ++++++++++++++++++++++++++++++-------
arch/arm64/mm/copypage.c | 3 ++-
arch/arm64/mm/flush.c | 14 +++++++----
4 files changed, 51 insertions(+), 14 deletions(-)
--
2.1.0
next reply other threads:[~2015-12-15 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 12:56 Ashok Kumar [this message]
2015-12-15 12:56 ` [PATCH v2 1/2] arm64: Defer dcache flush in __cpu_copy_user_page Ashok Kumar
2015-12-15 12:56 ` [PATCH v2 2/2] arm64: Use PoU cache instr for I/D coherency Ashok Kumar
2015-12-15 13:45 ` Mark Rutland
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=1450184178-28257-1-git-send-email-ashoks@broadcom.com \
--to=ashoks@broadcom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.