From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: fpsimd: avoid restoring fpcr if the contents haven't changed
Date: Fri, 27 Jun 2014 09:58:45 +0100 [thread overview]
Message-ID: <20140627085845.GD26276@arm.com> (raw)
In-Reply-To: <CAKv+Gu8rFmURfT9PLSQE4z91q5D03aoR7UOEJFSGRrBMXGsdOQ@mail.gmail.com>
On Thu, Jun 26, 2014 at 10:10:00PM +0100, Ard Biesheuvel wrote:
> Hey Will,
Hi Ard,
> On 26 June 2014 19:34, Will Deacon <will.deacon@arm.com> wrote:
> > Writing to the FPCR is commonly implemented as a self-synchronising
> > operation in the CPU, so avoid writing to the register when the saved
> > value matches that in the hardware already.
> >
> > Reviewed-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
> > ---
> > arch/arm64/include/asm/fpsimdmacros.h | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/arch/arm64/include/asm/fpsimdmacros.h b/arch/arm64/include/asm/fpsimdmacros.h
> > index 768414d55e64..137c0f45b0a8 100644
> > --- a/arch/arm64/include/asm/fpsimdmacros.h
> > +++ b/arch/arm64/include/asm/fpsimdmacros.h
> > @@ -40,6 +40,7 @@
> > str w\tmpnr, [\state, #16 * 2 + 4]
> > .endm
> >
> > +/* Clobbers \state */
> > .macro fpsimd_restore state, tmpnr
> > ldp q0, q1, [\state, #16 * 0]
> > ldp q2, q3, [\state, #16 * 2]
> > @@ -60,7 +61,15 @@
> > ldr w\tmpnr, [\state, #16 * 2]
> > msr fpsr, x\tmpnr
> > ldr w\tmpnr, [\state, #16 * 2 + 4]
> > + /*
> > + * Writes to fpcr may be self-synchronising, so avoid restoring
> > + * the register if it hasn't changed.
> > + */
> > + mrs \state, fpcr
> > + cmp x\tmpnr, \state
> > + b.eq 9999f
> > msr fpcr, x\tmpnr
> > +9999:
> > .endm
> >
>
> I would assume the same would apply to the partial restore that was
> merged during the last window?
Good point; I'll take a look.
Cheers,
Will
prev parent reply other threads:[~2014-06-27 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 17:34 [PATCH] arm64: fpsimd: avoid restoring fpcr if the contents haven't changed Will Deacon
2014-06-26 21:10 ` Ard Biesheuvel
2014-06-27 8:58 ` Will Deacon [this message]
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=20140627085845.GD26276@arm.com \
--to=will.deacon@arm.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 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).