From: Ingo Molnar <mingo@elte.hu>
To: Srinivasa Ds <srinivasa@in.ibm.com>
Cc: Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
paulus@samba.org, linuxppc-dev@ozlabs.org,
linux-parisc@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC][PATCH] Demultiplexing SIGTRAP signal
Date: Mon, 22 Sep 2008 16:54:04 +0200 [thread overview]
Message-ID: <20080922145404.GC27956@elte.hu> (raw)
In-Reply-To: <200809221841.27993.srinivasa@in.ibm.com>
* Srinivasa Ds <srinivasa@in.ibm.com> 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/ file should be modified instead.
(this problem will go away in v2.6.28 when we'll move include/asm-x86/
to arch/x86/include/)
> + si_code = get_si_code((unsigned long*)&condition);
coding style problem: please run checkpatch.
> /* Ok, finally something we can handle */
> - send_sigtrap(tsk, regs, error_code);
> + send_sigtrap(tsk, regs, error_code, si_code);
ok, that looks much nicer.
> - info.si_code = TRAP_BRKPT;
> + info.si_code = get_si_code(&condition);
no need to pass in the condition by reference.
> +#define TRAP_BRANCH (__SI_FAULT|3) /* process taken branch trap */
> +#define TRAP_HWBKPT (__SI_FAULT|4) /* hardware breakpoint or watchpoint
> */
stray linewrapped patch line - see Documentation/email-clients.txt.
> -void send_sigtrap(struct task_struct *tsk, struct pt_regs *regs, int
> error_code)
> +void send_sigtrap(struct task_struct *tsk, struct pt_regs *regs, int
> error_code,
linewrap.
> +++ linux-2.6.27-rc7/include/asm-x86/traps.h
> @@ -36,6 +36,16 @@ void do_invalid_op(struct pt_regs *, lon
> void do_general_protection(struct pt_regs *, long);
> void do_nmi(struct pt_regs *, long);
>
> +int get_si_code(unsigned long *condition)
> +{
> + if (*condition & DR_STEP)
> + return TRAP_TRACE;
please declare inline functions explicitly as 'static inline'.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Srinivasa Ds <srinivasa@in.ibm.com>
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, paulus@samba.org,
"H. Peter Anvin" <hpa@zytor.com>,
akpm@linux-foundation.org, Thomas Gleixner <tglx@linutronix.de>,
Roland McGrath <roland@redhat.com>
Subject: Re: [RFC][PATCH] Demultiplexing SIGTRAP signal
Date: Mon, 22 Sep 2008 16:54:04 +0200 [thread overview]
Message-ID: <20080922145404.GC27956@elte.hu> (raw)
In-Reply-To: <200809221841.27993.srinivasa@in.ibm.com>
* Srinivasa Ds <srinivasa@in.ibm.com> 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/ file should be modified instead.
(this problem will go away in v2.6.28 when we'll move include/asm-x86/
to arch/x86/include/)
> + si_code = get_si_code((unsigned long*)&condition);
coding style problem: please run checkpatch.
> /* Ok, finally something we can handle */
> - send_sigtrap(tsk, regs, error_code);
> + send_sigtrap(tsk, regs, error_code, si_code);
ok, that looks much nicer.
> - info.si_code = TRAP_BRKPT;
> + info.si_code = get_si_code(&condition);
no need to pass in the condition by reference.
> +#define TRAP_BRANCH (__SI_FAULT|3) /* process taken branch trap */
> +#define TRAP_HWBKPT (__SI_FAULT|4) /* hardware breakpoint or watchpoint
> */
stray linewrapped patch line - see Documentation/email-clients.txt.
> -void send_sigtrap(struct task_struct *tsk, struct pt_regs *regs, int
> error_code)
> +void send_sigtrap(struct task_struct *tsk, struct pt_regs *regs, int
> error_code,
linewrap.
> +++ linux-2.6.27-rc7/include/asm-x86/traps.h
> @@ -36,6 +36,16 @@ void do_invalid_op(struct pt_regs *, lon
> void do_general_protection(struct pt_regs *, long);
> void do_nmi(struct pt_regs *, long);
>
> +int get_si_code(unsigned long *condition)
> +{
> + if (*condition & DR_STEP)
> + return TRAP_TRACE;
please declare inline functions explicitly as 'static inline'.
Ingo
next prev parent reply other threads:[~2008-09-22 14:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 10:32 [RFC][PATCH] Demultiplexing SIGTRAP signal Srinivasa Ds
2008-09-22 10:42 ` Ingo Molnar
2008-09-22 10:42 ` Ingo Molnar
2008-09-22 13:11 ` Srinivasa Ds
2008-09-22 13:11 ` Srinivasa Ds
2008-09-22 14:54 ` Ingo Molnar [this message]
2008-09-22 14:54 ` Ingo Molnar
2008-09-23 9:53 ` Srinivasa Ds
2008-09-23 9:53 ` Srinivasa Ds
2008-09-23 11:28 ` Ingo Molnar
2008-09-23 11:28 ` Ingo Molnar
2008-09-23 11:30 ` Ingo Molnar
2008-09-23 11:30 ` Ingo Molnar
2008-09-23 14:25 ` [RFC][PATCH] Demultiplexing SIGTRAP signal -v2 Srinivasa Ds
2008-09-23 14:25 ` Srinivasa Ds
2008-09-23 14:31 ` Ingo Molnar
2008-09-23 14:31 ` Ingo Molnar
2008-09-26 9:06 ` Roland McGrath
2008-09-26 9:06 ` Roland McGrath
2008-09-26 9:06 ` Roland McGrath
2008-09-29 13:34 ` Srinivasa DS
2008-09-29 13:34 ` Srinivasa DS
2008-09-23 15:53 ` Gabriel Paubert
2008-09-23 15:53 ` Gabriel Paubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080922145404.GC27956@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=roland@redhat.com \
--cc=srinivasa@in.ibm.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.