Re: Making __copy_tofrom_user more readable for powerpc (arch/powerpc/lib/copy_32.S)

2008-07-11 Thread Arnd Bergmann
On Friday 11 July 2008, prodyut hazarika wrote: > I have a version which just keeps a count of bytes copied till any > fault happened. Then for any exception, I just substract this value > from the total number of bytes to be copied, and store in r3 and > return back. This is the common fixup code

Re: Making __copy_tofrom_user more readable for powerpc (arch/powerpc/lib/copy_32.S)

2008-07-10 Thread Michael Neuling
In message <[EMAIL PROTECTED]> you wro te: > Hi all, > I am trying to optimize the __copy_tofrom_user function for PPC4xx, > and I would want to know why the exception handling code has been made > so complicated. All the fixup code should do is to store the number of > bytes that failed in copy in

Making __copy_tofrom_user more readable for powerpc (arch/powerpc/lib/copy_32.S)

2008-07-10 Thread prodyut hazarika
Hi all, I am trying to optimize the __copy_tofrom_user function for PPC4xx, and I would want to know why the exception handling code has been made so complicated. All the fixup code should do is to store the number of bytes that failed in copy in r3 and return back. The current code tries to copy

Making __copy_tofrom_user more readable for powerpc (arch/powerpc/lib/copy_32.S)

2008-07-10 Thread prodyut hazarika
Hi all, I am trying to optimize the __copy_tofrom_user function for PPC4xx, and I would want to know why the exception handling code has been made so complicated. All the fixup code should do is to store the number of bytes that failed in copy in r3 and return back. The current code tries to copy