linux-kernel - Re: [RFC PATCH] arm64/fpsimd: Don't disable softirq when touching FPSIMD/SVE state

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]

Message-ID: <715fed53-7c2d-f5fd-813b-211b204475d6@arm.com>
Date:   Fri, 15 Mar 2019 10:22:43 +0000
From:   Julien Grall <julien.grall@....com>
To:     Dave Martin <Dave.Martin@....com>
Cc:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-rt-users@...r.kernel.org,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will.deacon@....com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] arm64/fpsimd: Don't disable softirq when touching
 FPSIMD/SVE state



On 15/03/2019 10:06, Dave Martin wrote:
> On Thu, Mar 14, 2019 at 06:07:19PM +0000, Julien Grall wrote:
>> Hi Sebastian,
>>
>> On 3/4/19 5:25 PM, Sebastian Andrzej Siewior wrote:
> 
> [...]
> 
>>> It would increase the softirq latency but the question is how bad would
>>> it be. It would continue once the SIMD section is done.
>>
>> On Arm, the kernel may use either FPSIMD or SVE (if supported by the
>> platform). While the FPSIMD context is fairly small (~4K), the SVE context
>> can be up to ~64KB.
> 
> It's not quite as bad as that.  The FPSIMD state is ~0.5K, with the SVE
> state size being up to ~8.5K (though for today's implementations ~2K may
> be considered typical).

Whoops, I forgot to divide by 8. Thank you for spotting it!

Cheers,

-- 
Julien Grall