From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751607AbdLARPN (ORCPT ); Fri, 1 Dec 2017 12:15:13 -0500 Received: from merlin.infradead.org ([205.233.59.134]:36888 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750782AbdLARPM (ORCPT ); Fri, 1 Dec 2017 12:15:12 -0500 Date: Fri, 1 Dec 2017 18:14:58 +0100 From: Peter Zijlstra To: Sebastian Andrzej Siewior Cc: Mark Rutland , linux-rt-users@vger.kernel.org, Catalin Marinas , Will Deacon , linux-kernel@vger.kernel.org, Steven Rostedt , tglx@linutronix.de, linux-arm-kernel@lists.infradead.org, ard.biesheuvel@linaro.org Subject: Re: [PATCH RT] arm*: disable NEON in kernel mode Message-ID: <20171201171458.3a2acsltiq54gvuu@hirez.programming.kicks-ass.net> References: <20171130142216.GB12606@linutronix.de> <20171130143028.GA1351@linutronix.de> <20171201104331.GB1612@linutronix.de> <20171201134506.GF1612@linutronix.de> <20171201141827.yip6pl3tt7kxzek7@lakrids.cambridge.arm.com> <20171201143648.GK1612@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171201143648.GK1612@linutronix.de> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 01, 2017 at 03:36:48PM +0100, Sebastian Andrzej Siewior wrote: > On 2017-12-01 14:18:28 [+0000], Mark Rutland wrote: > > [Adding Ard, who wrote the NEON crypto code] > > > > On Fri, Dec 01, 2017 at 02:45:06PM +0100, Sebastian Andrzej Siewior wrote: > > > +arm folks, to let you know > > > > > > On 2017-12-01 11:43:32 [+0100], To linux-rt-users@vger.kernel.org wrote: > > > > NEON in kernel mode is used by the crypto algorithms and raid6 code. > > > > While the raid6 code looks okay, the crypto algorithms do not: NEON > > > > is enabled on first invocation and may allocate/free/map memory before > > > > the NEON mode is disabled again. > > > > Could you elaborate on why this is a problem? > > > > I guess this is because kernel_neon_{begin,end}() disable preemption? > > > > ... is this specific to RT? > > It is RT specific, yes. One thing are the unbounded latencies since > everything in this preempt_disable section can take time depending on > the size of the request. Well, PREEMPT cares about that too.