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: Tue, 23 Sep 2008 13:28:12 +0200 [thread overview]
Message-ID: <20080923112812.GL29021@elte.hu> (raw)
In-Reply-To: <200809231523.52802.srinivasa@in.ibm.com>
* Srinivasa Ds <srinivasa@in.ibm.com> wrote:
> On Monday 22 September 2008 20:24:04 Ingo Molnar wrote:
> > * 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/)
> >
>
> Ingo, Sorry if I have confused you. [...]
hah, indeed - i mis-read them as include/asm/.
> Currently a SIGTRAP can denote any one of below reasons.
> - Breakpoint hit
> - H/W debug register hit
> - Single step
> - Signal sent through kill() or rasie()
>
> Architectures like powerpc/parisc provides infrastructure to
> demultiplex SIGTRAP signal 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.
applied to [the new topic] tip/core/signal, thanks Srinivasa! There are
some other pending x86 signal changes already, so i based
tip/core/signal on tip/x86/signal.
Roland, any opinion on this change?
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: Tue, 23 Sep 2008 13:28:12 +0200 [thread overview]
Message-ID: <20080923112812.GL29021@elte.hu> (raw)
In-Reply-To: <200809231523.52802.srinivasa@in.ibm.com>
* Srinivasa Ds <srinivasa@in.ibm.com> wrote:
> On Monday 22 September 2008 20:24:04 Ingo Molnar wrote:
> > * 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/)
> >
>
> Ingo, Sorry if I have confused you. [...]
hah, indeed - i mis-read them as include/asm/.
> Currently a SIGTRAP can denote any one of below reasons.
> - Breakpoint hit
> - H/W debug register hit
> - Single step
> - Signal sent through kill() or rasie()
>
> Architectures like powerpc/parisc provides infrastructure to
> demultiplex SIGTRAP signal 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.
applied to [the new topic] tip/core/signal, thanks Srinivasa! There are
some other pending x86 signal changes already, so i based
tip/core/signal on tip/x86/signal.
Roland, any opinion on this change?
Ingo
next prev parent reply other threads:[~2008-09-23 11:28 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
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 [this message]
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=20080923112812.GL29021@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.