diff options
| author | Michael Ellerman <mpe@ellerman.id.au> | 2014-12-05 21:16:59 +1100 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2015-02-02 14:51:31 +1100 |
| commit | 4c3b21686111e0ac6018469dacbc5549f9915cf8 (patch) | |
| tree | c35cd7351ce892e64a8a271de72317d4e0945637 /arch/powerpc/kernel/syscalls.c | |
| parent | 6f963ec2d6bf2476a16799eece920acb2100ff1c (diff) | |
powerpc/kernel: Make syscall_exit a local label
Currently when we back trace something that is in a syscall we see
something like this:
[c000000000000000] [c000000000000000] SyS_read+0x6c/0x110
[c000000000000000] [c000000000000000] syscall_exit+0x0/0x98
Although it's entirely correct, seeing syscall_exit at the bottom can be
confusing - we were exiting from a syscall and then called SyS_read() ?
If we instead change syscall_exit to be a local label we get something
more intuitive:
[c0000001fa46fde0] [c00000000026719c] SyS_read+0x6c/0x110
[c0000001fa46fe30] [c000000000009264] system_call+0x38/0xd0
ie. we were handling a system call, and it was SyS_read().
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'arch/powerpc/kernel/syscalls.c')
0 files changed, 0 insertions, 0 deletions