the si_code logic there, and just
pass it the hardware bits or let it get them from the thread_struct
(trap_nr, error_code, debugreg6).
That sounds like a good idea. Let me go through code and get back to you.
Thanks
Srinivasa DS
___
Linuxppc-dev
On Monday 22 September 2008 20:24:04 Ingo Molnar wrote:
* Srinivasa Ds [EMAIL PROTECTED] wrote:
--- linux-2.6.27-rc7.orig/arch/ia64/include/asm/siginfo.h
+++ linux-2.6.27-rc7/arch/ia64/include/asm/siginfo.h
please do not send patches that modify include/asm/ files, the
include/asm-x86
by extending it to x86 and x86_64 archs.
Signed-off-by: Srinivasa DS [EMAIL PROTECTED]
---
arch/ia64/include/asm/siginfo.h|5 -
arch/powerpc/include/asm/siginfo.h |5 -
arch/x86/kernel/ptrace.c |7 ---
arch/x86/kernel/traps_32.c |4 +++-
arch/x86
by passing down the information for receiving SIGTRAP through
si_code of siginfot_t structure. Here is an attempt is generalise this
infrastructure by extending it to x86 and x86_64 archs.
Signed-off-by: Srinivasa DS [EMAIL PROTECTED]
---
arch/ia64/include/asm/siginfo.h|5 -
arch/powerpc
archs.
Signed-off-by: Srinivasa DS [EMAIL PROTECTED]
---
arch/ia64/include/asm/siginfo.h|5 -
arch/powerpc/include/asm/siginfo.h |5 -
arch/x86/kernel/ptrace.c |7 ---
arch/x86/kernel/traps_32.c |4 +++-
arch/x86/kernel/traps_64.c |2
+445,6 @@ long arch_ptrace(struct task_struct *child, long
request, long addr, long data)
break;
}
Thanks
Srinivasa DS
Linux Technology Centre
IBM.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman