From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: use memset to clear BSS
Date: Wed, 6 Jan 2016 12:34:05 +0000 [thread overview]
Message-ID: <20160106123404.GG563@leverpostej> (raw)
In-Reply-To: <20160106114039.GE563@leverpostej>
On Wed, Jan 06, 2016 at 11:40:39AM +0000, Mark Rutland wrote:
> On Wed, Jan 06, 2016 at 12:12:45PM +0100, Ard Biesheuvel wrote:
> > On 6 January 2016 at 12:05, Mark Rutland <mark.rutland@arm.com> wrote:
> > > Currently we use an open-coded memzero to clear the BSS. As it is a
> > > trivial implementation, it is sub-optimal.
> > >
> > > Our optimised memset doesn't use the stack, is position-independent, and
> > > for the memzero case can use of DC ZVA to clear large blocks
> > > efficiently. In __mmap_switched the MMU is on and there are no live
> > > caller-saved registers, so we can safely call an uninstrumented memset.
> > >
> > > This patch changes __mmap_switched to use memset when clearing the BSS.
> > > We use the __pi_memset alias so as to avoid any instrumentation in all
> > > kernel configurations. As with the head symbols, we must get the linker
> > > to generate __bss_size, as there is no ELF relocation for the
> > > subtraction of two symbols.
> > >
> > > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > > Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > > Cc: Marc Zyngier <marc.zyngier@arm.com>
> > > Cc: Will Deacon <will.deacon@arm.com>
> > > ---
> > > arch/arm64/kernel/head.S | 14 ++++++--------
> > > arch/arm64/kernel/image.h | 2 ++
> > > 2 files changed, 8 insertions(+), 8 deletions(-)
> > >
> > > diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S
> > > index 23cfc08..247a97b 100644
> > > --- a/arch/arm64/kernel/head.S
> > > +++ b/arch/arm64/kernel/head.S
> > > @@ -415,14 +415,12 @@ ENDPROC(__create_page_tables)
> > > */
> > > .set initial_sp, init_thread_union + THREAD_START_SP
> > > __mmap_switched:
> > > - adr_l x6, __bss_start
> > > - adr_l x7, __bss_stop
> > > -
> > > -1: cmp x6, x7
> > > - b.hs 2f
> > > - str xzr, [x6], #8 // Clear BSS
> > > - b 1b
> > > -2:
> > > + // clear BSS
> > > + adr_l x0, __bss_start
> > > + mov x1, xzr
> > > + mov_l x2, __bss_size
> >
> > Is it such a big deal to do
> >
> > adr_l x2, __bss_stop
> > sub x2, x2, x0
> >
> > instead?
>
> I'm happy either way.
>
> It no-one else has a use for mov_l I'll drop it and move to that.
>From a discussion with Will, it sounds like the sub form is preferable,
so I'll drop mov_l for now.
Thanks,
Mark.
next prev parent reply other threads:[~2016-01-06 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 11:05 [PATCH 1/2] arm64: add macro to handle large immediates Mark Rutland
2016-01-06 11:05 ` [PATCH 2/2] arm64: use memset to clear BSS Mark Rutland
2016-01-06 11:12 ` Ard Biesheuvel
2016-01-06 11:40 ` Mark Rutland
2016-01-06 12:34 ` Mark Rutland [this message]
2016-01-06 11:15 ` [PATCH 1/2] arm64: add macro to handle large immediates Ard Biesheuvel
2016-01-06 12:21 ` Mark Rutland
2016-01-06 12:26 ` Ard Biesheuvel
2016-01-06 12:37 ` 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=20160106123404.GG563@leverpostej \
--to=mark.rutland@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).