Searched hist:"6873 def90016cc1cde03c38e10a80146d980b48a" (Results 1 – 4 of 4) sorted by relevance
/linux/tools/testing/selftests/powerpc/pmu/ebb/ |
H A D | busy_loop.S | 6873def90016cc1cde03c38e10a80146d980b48a Wed Jul 23 09:31:33 CEST 2014 Michael Ellerman <mpe@ellerman.id.au> selftests/powerpc: Move core_busy_loop() into asm
There is at least one bug in core_busy_loop(), we use r0, but it's not in the clobber list. We were getting away with this it seems but that was luck.
It's also fishy to be touching the stack, even if we do it below the stack pointer. It seems we get away with it, but looking at the generated code that may just be luck.
So move it into assembler, do all the stack handling by hand. We create a stack frame to save the non-volatiles in, so we can muck around with them.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
|
H A D | ebb.h | diff 6873def90016cc1cde03c38e10a80146d980b48a Wed Jul 23 09:31:33 CEST 2014 Michael Ellerman <mpe@ellerman.id.au> selftests/powerpc: Move core_busy_loop() into asm
There is at least one bug in core_busy_loop(), we use r0, but it's not in the clobber list. We were getting away with this it seems but that was luck.
It's also fishy to be touching the stack, even if we do it below the stack pointer. It seems we get away with it, but looking at the generated code that may just be luck.
So move it into assembler, do all the stack handling by hand. We create a stack frame to save the non-volatiles in, so we can muck around with them.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
|
H A D | ebb.c | diff 6873def90016cc1cde03c38e10a80146d980b48a Wed Jul 23 09:31:33 CEST 2014 Michael Ellerman <mpe@ellerman.id.au> selftests/powerpc: Move core_busy_loop() into asm
There is at least one bug in core_busy_loop(), we use r0, but it's not in the clobber list. We were getting away with this it seems but that was luck.
It's also fishy to be touching the stack, even if we do it below the stack pointer. It seems we get away with it, but looking at the generated code that may just be luck.
So move it into assembler, do all the stack handling by hand. We create a stack frame to save the non-volatiles in, so we can muck around with them.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
|
H A D | Makefile | diff 6873def90016cc1cde03c38e10a80146d980b48a Wed Jul 23 09:31:33 CEST 2014 Michael Ellerman <mpe@ellerman.id.au> selftests/powerpc: Move core_busy_loop() into asm
There is at least one bug in core_busy_loop(), we use r0, but it's not in the clobber list. We were getting away with this it seems but that was luck.
It's also fishy to be touching the stack, even if we do it below the stack pointer. It seems we get away with it, but looking at the generated code that may just be luck.
So move it into assembler, do all the stack handling by hand. We create a stack frame to save the non-volatiles in, so we can muck around with them.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
|