From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Roland McGrath <roland@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
john.blackwood@ccur.com, linux-kernel@vger.kernel.org,
Sven-Thorsten Dietrich <sdietrich@novell.com>,
bugsy@ccur.com
Subject: Re: [RFC] [PATCH] selective signal ptracing
Date: Tue, 19 Jun 2007 11:15:00 +1000 [thread overview]
Message-ID: <1182215700.26853.299.camel@localhost.localdomain> (raw)
In-Reply-To: <625fc13d0706180615t2f327b16rf648b2ee56da6ed9@mail.gmail.com>
On Mon, 2007-06-18 at 08:15 -0500, Josh Boyer wrote:
> On 6/16/07, Roland McGrath <roland@redhat.com> wrote:
> > > What are the issues with arch like ARM ?
> >
> > The interesting class ARM belongs to is machines that don't (or don't
> > always) have hardware support for single-step. Maintaining the status quo
> > of how PTRACE_SINGLESTEP functions on these machines is different in
> > implementation under utrace than it is for machines that always use
> > hardware support. That is the only special complication for ARM, and it is
> > not really very complicated. Apparently the way I described the issue in
> > the past was easily misunderstood.
>
> That isn't just ARM. There are some embedded PowerPC chips that lack
> an easily usable hardware single step. Just an FYI.
Note that we could use xmon infrastructure for that ... Paul has the
whole shebang done in there, including emulating branches etc...
Ben.
next prev parent reply other threads:[~2007-06-19 1:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 14:32 [RFC] [PATCH] selective signal ptracing John Blackwood
2007-06-15 19:42 ` Roland McGrath
2007-06-15 23:26 ` Alan Cox
2007-06-15 23:39 ` Roland McGrath
2007-06-17 0:11 ` Benjamin Herrenschmidt
2007-06-17 1:29 ` Roland McGrath
2007-06-18 13:15 ` Josh Boyer
2007-06-19 1:15 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-16 9:24 Oleg Nesterov
2007-06-18 19:24 John Blackwood
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=1182215700.26853.299.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bugsy@ccur.com \
--cc=john.blackwood@ccur.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=sdietrich@novell.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox