From: Robin Murphy <robin.murphy@arm.com>
To: Reiji Watanabe <reijiw@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: Marc Zyngier <maz@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Peter Collingbourne <pcc@google.com>,
Evgenii Stepanov <eugenis@google.com>,
linux-arm-kernel@lists.infradead.org,
Peter Shier <pshier@google.com>,
Ricardo Koller <ricarkol@google.com>,
Oliver Upton <oupton@google.com>,
Jing Zhang <jingzhangos@google.com>,
Raghavendra Rao Anata <rananta@google.com>
Subject: Re: [PATCH v2 1/2] arm64: clear_page() shouldn't use DC ZVA when DCZID_EL0.DZP == 1
Date: Tue, 16 Nov 2021 23:00:00 +0000 [thread overview]
Message-ID: <574b481a-900c-3f91-9967-d117cde69a44@arm.com> (raw)
In-Reply-To: <20211108071149.823570-2-reijiw@google.com>
On 2021-11-08 07:11, Reiji Watanabe wrote:
> Currently, clear_page() uses DC ZVA instruction unconditionally. But it
> should make sure that DCZID_EL0.DZP, which indicates whether or not use
> of DC ZVA instruction is prohibited, is zero when using the instruction.
> Use STP as memset does instead when DCZID_EL0.DZP == 1.
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
FWIW I did eventually figure out the "pre-bias" trick from v1 thanks to
Mark's nod toward the original context, but a quick survey of various
optimisation guides implied that the explicit add should generally be
preferred over post-index writeback anyway, so I think we're all good here.
Cheers,
Robin.
> Fixes: f27bb139c387 ("arm64: Miscellaneous library functions")
> Signed-off-by: Reiji Watanabe <reijiw@google.com>
> ---
> arch/arm64/lib/clear_page.S | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm64/lib/clear_page.S b/arch/arm64/lib/clear_page.S
> index b84b179edba3..ea3a6c927fe8 100644
> --- a/arch/arm64/lib/clear_page.S
> +++ b/arch/arm64/lib/clear_page.S
> @@ -16,6 +16,7 @@
> */
> SYM_FUNC_START_PI(clear_page)
> mrs x1, dczid_el0
> + tbnz x1, #4, 2f /* Branch if DC ZVA is prohibited */
> and w1, w1, #0xf
> mov x2, #4
> lsl x1, x2, x1
> @@ -25,5 +26,14 @@ SYM_FUNC_START_PI(clear_page)
> tst x0, #(PAGE_SIZE - 1)
> b.ne 1b
> ret
> +
> +2: stp xzr, xzr, [x0]
> + stp xzr, xzr, [x0, #16]
> + stp xzr, xzr, [x0, #32]
> + stp xzr, xzr, [x0, #48]
> + add x0, x0, #64
> + tst x0, #(PAGE_SIZE - 1)
> + b.ne 2b
> + ret
> SYM_FUNC_END_PI(clear_page)
> EXPORT_SYMBOL(clear_page)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-16 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 7:11 [PATCH v2 0/2] arm64: DC {ZVA,GVA,GZVA} shouldn't be used when DCZID_EL0.DZP == 1 Reiji Watanabe
2021-11-08 7:11 ` [PATCH v2 1/2] arm64: clear_page() shouldn't use DC ZVA " Reiji Watanabe
2021-11-16 23:00 ` Robin Murphy [this message]
2021-11-18 8:18 ` Reiji Watanabe
2021-11-18 11:42 ` Robin Murphy
2021-11-08 7:11 ` [PATCH v2 2/2] arm64: mte: DC {GVA,GZVA} shouldn't be used " Reiji Watanabe
2021-12-03 18:29 ` Catalin Marinas
2021-12-03 18:51 ` Catalin Marinas
2021-12-04 8:03 ` Reiji Watanabe
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=574b481a-900c-3f91-9967-d117cde69a44@arm.com \
--to=robin.murphy@arm.com \
--cc=catalin.marinas@arm.com \
--cc=eugenis@google.com \
--cc=jingzhangos@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@google.com \
--cc=pcc@google.com \
--cc=pshier@google.com \
--cc=rananta@google.com \
--cc=reijiw@google.com \
--cc=ricarkol@google.com \
--cc=will@kernel.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