diff options
author | Geert Uytterhoeven <geert@linux-m68k.org> | 2013-06-09 18:12:42 (GMT) |
---|---|---|
committer | Geert Uytterhoeven <geert@linux-m68k.org> | 2013-06-24 17:44:19 (GMT) |
commit | 631d8b674f5f8235e9cb7e628b0fe9e5200e3158 (patch) | |
tree | 94cfb3bcdfbff1ddea8ef4a511fe92ca06cf9e31 /arch/arc/plat-tb10x | |
parent | 957d6bf665462eb1e94f7c23b4bdf20a83fea4b2 (diff) | |
download | linux-fsl-qoriq-631d8b674f5f8235e9cb7e628b0fe9e5200e3158.tar.xz |
m68k/uaccess: Fix asm constraints for userspace access
When compiling a MMU kernel with CPU_HAS_ADDRESS_SPACES=n (e.g. "MMU=y
allnoconfig": "echo CONFIG_MMU=y > allno.config && make KCONFIG_ALLCONFIG=1
allnoconfig"), we use plain "move" instead of "moves", and I got:
CC arch/m68k/lib/uaccess.o
{standard input}: Assembler messages:
{standard input}:47: Error: operands mismatch -- statement `move.b %a0,(%a1)' ignored
This happens because plain "move" doesn't support byte transfers between
memory and address registers, while "moves" does.
Fix the asm constraints for __generic_copy_from_user(),
__generic_copy_to_user(), and __clear_user() to only use data registers
when accessing userspace.
Also, relax the asm constraints for 16-bit userspace accesses in
__put_user() and __get_user(), as both "move" and "moves" do support
such transfers between memory and address registers.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Diffstat (limited to 'arch/arc/plat-tb10x')
0 files changed, 0 insertions, 0 deletions