linux-kernel - RE: [PATCH v3 0/1] arm64: Add workaround for Fujitsu A64FX erratum 010001

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 5 Feb 2019 13:32:07 +0000
From:   "Zhang, Lei" <zhang.lei@...fujitsu.com>
To:     'Will Deacon' <will.deacon@....com>
CC:     'Mark Rutland' <mark.rutland@....com>,
        'Catalin Marinas' <catalin.marinas@....com>,
        'James Morse' <james.morse@....com>,
        "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
        "'linux-arm-kernel@...ts.infradead.org'" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH v3 0/1] arm64: Add workaround for Fujitsu A64FX erratum
 010001

Hi Will,

> -----Original Message-----
> From: linux-arm-kernel
> [mailto:linux-arm-kernel-bounces@...ts.infradead.org] On Behalf Of
> Will Deacon
> Sent: Friday, February 01, 2019 7:52 PM
> To: Zhang, Lei 
> Cc: 'Mark Rutland'; 'Catalin Marinas'; 'James Morse';
> 'linux-kernel@...r.kernel.org';
> 'linux-arm-kernel@...ts.infradead.org'
> Subject: Re: [PATCH v3 0/1] arm64: Add workaround for Fujitsu A64FX
> erratum 010001

> So I guess we should boot with NFD1 clear, and then set it only when we
> realise we're not on an A64FX?

In my patch, I do similar things at __cpu_setup which we 
set NFD1=1 on all processors except A64FX.

Do you mean we would better to change the place where we 
set/clear NFD1?

Thanks,
Zhang Lei