Re: [PATCH V2 8/8] powerpc: Add the ability to save VSX without giving it up

2016-01-17 Thread Michael Neuling
> > Also, put the #ifdef junk as part of the function so that the caller > > doesn't have to deal with it. > > > > Can do absolutely, however this means that in save_all I can't check if the > function needs to be called or not. For example, without CONFIG_VSX, MSR_VSX > won't exist which

Re: [PATCH V2 8/8] powerpc: Add the ability to save VSX without giving it up

2016-01-17 Thread Cyril Bur
On Fri, 15 Jan 2016 17:25:26 +1100 Michael Neuling wrote: > On Fri, 2016-01-15 at 16:04 +1100, Cyril Bur wrote: > > This patch adds the ability to be able to save the VSX registers to > > the > > thread struct without giving up (disabling the facility) next time > > the > >

Re: [PATCH V2 8/8] powerpc: Add the ability to save VSX without giving it up

2016-01-14 Thread Michael Neuling
On Fri, 2016-01-15 at 16:04 +1100, Cyril Bur wrote: > This patch adds the ability to be able to save the VSX registers to > the > thread struct without giving up (disabling the facility) next time > the > process returns to userspace. > > This patch builds on a previous optimisation for the FPU

[PATCH V2 8/8] powerpc: Add the ability to save VSX without giving it up

2016-01-14 Thread Cyril Bur
This patch adds the ability to be able to save the VSX registers to the thread struct without giving up (disabling the facility) next time the process returns to userspace. This patch builds on a previous optimisation for the FPU and VEC registers in the thread copy path to avoid a possibly