mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: 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: Sat, 16 Jun 2007 18:29:52 -0700 (PDT)	[thread overview]
Message-ID: <20070617012952.09F2D4D059F@magilla.localdomain> (raw)
In-Reply-To: Benjamin Herrenschmidt's message of  Sunday, 17 June 2007 10:11:02 +1000 <1182039062.26853.111.camel@localhost.localdomain>

> 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.

> Also, is there a mail thread or paper somewhere describing utrace, its
> interfaces and what's needed to hook it up on a platform ?

See http://redhat.com/~roland/utrace/ for the patches and a porting howto.
The patches add a Documentation/ file and kerneldoc stuff for the interfaces.


Thanks,
Roland

  reply	other threads:[~2007-06-17  1:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15 14:32 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 [this message]
2007-06-18 13:15         ` Josh Boyer
2007-06-19  1:15           ` Benjamin Herrenschmidt
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=20070617012952.09F2D4D059F@magilla.localdomain \
    --to=roland@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=bugsy@ccur.com \
    --cc=john.blackwood@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --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
all inboxes | Powered by JetHome®