From: "Zhang, Lei" <zhang.lei@jp.fujitsu.com>
To: 'James Morse' <james.morse@arm.com>
Cc: 'Mark Rutland' <mark.rutland@arm.com>,
'Catalin Marinas' <catalin.marinas@arm.com>,
"'will.deacon@arm.com'" <will.deacon@arm.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v3 0/1] arm64: Add workaround for Fujitsu A64FX erratum 010001
Date: Fri, 1 Feb 2019 05:53:50 +0000 [thread overview]
Message-ID: <8898674D84E3B24BA3A2D289B872026A6A3090AC@G01JPEXMBKW03> (raw)
In-Reply-To: <cb7544e2-bd85-df4c-1f48-0afeedefc962@arm.com>
Hi James,
> -----Original Message-----
> From: linux-arm-kernel
> [mailto:linux-arm-kernel-bounces@lists.infradead.org] On Behalf Of
> James Morse
> Sent: Thursday, January 31, 2019 12:00 AM
> To: Zhang, Lei/張 雷
> Cc: 'Mark Rutland'; 'Catalin Marinas'; 'will.deacon@arm.com';
> 'linux-kernel@vger.kernel.org';
> 'linux-arm-kernel@lists.infradead.org'
> Subject: Re: [PATCH v3 0/1] arm64: Add workaround for Fujitsu A64FX
> erratum 010001
>
>
> e03e61c3173c ("arm64: kaslr: Set TCR_EL1.NFD1 when
> CONFIG_RANDOMIZE_BASE=y") ?
>
> So you'd never see it if you disabled CONFIG_RANDOMIZE_BASE?
For security, it is necessary to set CONFIG_RANDOMIZE_BASE=y.
Thanks,
Zhang Lei
next prev parent reply other threads:[~2019-02-01 5:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 12:29 [PATCH v3 0/1] arm64: Add workaround for Fujitsu A64FX erratum 010001 Zhang, Lei
2019-01-29 18:10 ` Catalin Marinas
2019-01-30 14:56 ` James Morse
2019-02-05 12:49 ` Zhang, Lei
2019-01-30 15:00 ` James Morse
2019-02-01 5:53 ` Zhang, Lei [this message]
2019-02-01 10:51 ` Will Deacon
2019-02-05 13:32 ` Zhang, Lei
2019-02-13 13:19 ` Will Deacon
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=8898674D84E3B24BA3A2D289B872026A6A3090AC@G01JPEXMBKW03 \
--to=zhang.lei@jp.fujitsu.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.com \
/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).