Re: [PATCH resend 03/15] arm64: defer reloading a task's FPSIMD state to userland resume

2014-05-06 Thread Catalin Marinas
On Thu, May 01, 2014 at 04:49:35PM +0100, Ard Biesheuvel wrote: @@ -153,12 +252,11 @@ static int fpsimd_cpu_pm_notifier(struct notifier_block *self, { switch (cmd) { case CPU_PM_ENTER: - if (current-mm) + if (current-mm

Re: [PATCH resend 03/15] arm64: defer reloading a task's FPSIMD state to userland resume

2014-05-06 Thread Ard Biesheuvel
On 6 May 2014 18:08, Catalin Marinas catalin.mari...@arm.com wrote: On Thu, May 01, 2014 at 04:49:35PM +0100, Ard Biesheuvel wrote: @@ -153,12 +252,11 @@ static int fpsimd_cpu_pm_notifier(struct notifier_block *self, { switch (cmd) { case CPU_PM_ENTER: - if

Re: [PATCH resend 03/15] arm64: defer reloading a task's FPSIMD state to userland resume

2014-05-06 Thread Catalin Marinas
On Tue, May 06, 2014 at 05:25:14PM +0100, Ard Biesheuvel wrote: On 6 May 2014 18:08, Catalin Marinas catalin.mari...@arm.com wrote: On Thu, May 01, 2014 at 04:49:35PM +0100, Ard Biesheuvel wrote: @@ -153,12 +252,11 @@ static int fpsimd_cpu_pm_notifier(struct notifier_block *self, {

[PATCH resend 03/15] arm64: defer reloading a task's FPSIMD state to userland resume

2014-05-01 Thread Ard Biesheuvel
If a task gets scheduled out and back in again and nothing has touched its FPSIMD state in the mean time, there is really no reason to reload it from memory. Similarly, repeated calls to kernel_neon_begin() and kernel_neon_end() will preserve and restore the FPSIMD state every time. This patch