linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Roland McGrath <roland@redhat.com>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: utrace comments
Date: Mon, 30 Apr 2007 10:33:31 +0100	[thread overview]
Message-ID: <20070430093331.GB11345@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070430092200.GA15773@lst.de>

On Mon, Apr 30, 2007 at 11:22:00AM +0200, Christoph Hellwig wrote:
> On Mon, Apr 30, 2007 at 10:18:09AM +0100, Russell King wrote:
> > Roland's idea of single-stepping is that it *must* be supported by
> > hardware for utrace to use it.  There are a number of architectures
> > which can only do single-stepping by modifying the text of the
> > program being single stepped.  ARM is one such example.
> > 
> > As such, even when utrace is complete, some architectures will never
> > support in-kernel single step with utrace.  I believe Roland's idea
> > is to have single step supported on these via some vapourware userspace
> > library.
> 
> Does the current arm ptrace code support single stepping in kernelspace?
> If yes we absolutely need to continue to support it.

single stepping of user space code via standard ptrace calls, yes.

> > I'd also like to see utrace become *optional*
> > for architectures to support, rather than as it currently stands as
> > a *mandatory* requirement when merged.
> 
> No way we'd keep both the old ptrace mess and utrace in the same tree.

Given the stated arguments from yourself and Roland, that only leaves
one solution to that.

I have no real problem with a decision being made to drop kernel-based
single stepping _provided_ we have some replacement strategy in place
and readily available.  At the moment I've not seen such a strategy.

I'm not sure if Roland's expecting architecture maintainers to
create such a strategy themselves - which would probably turn out to
being far worse since you could end up with different implementations
for each architecture.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2007-04-30  9:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 16:51 utrace comments Christoph Hellwig
2006-12-05  9:51 ` Roland McGrath
2006-12-06 21:58   ` Christoph Hellwig
2007-04-30  4:02 ` Roland McGrath
2007-04-30  9:08   ` Christoph Hellwig
2007-04-30  9:18     ` Russell King
2007-04-30  9:22       ` Christoph Hellwig
2007-04-30  9:33         ` Russell King [this message]
2007-04-30  9:45           ` Russell King
2007-04-30 10:32             ` Christoph Hellwig
2007-04-30 10:18           ` Christoph Hellwig
2007-06-22  2:40           ` Roland McGrath
2007-05-10  8:49     ` Roland McGrath
2007-04-30  9:11   ` condingstyle, was " Christoph Hellwig
2007-04-30 17:09     ` Andrew Morton
2007-04-30 18:19       ` Jan Engelhardt
2007-04-30 18:39       ` Daniel Hazelton
2007-04-30 18:42       ` Satyam Sharma
2007-04-30 22:18         ` Stefan Richter
2007-05-01  9:00         ` Geert Uytterhoeven
2007-05-01 13:11           ` Scott Preece
2007-05-01 14:16           ` David Woodhouse
2007-05-01 15:00             ` John Anthony Kazos Jr.
2007-05-01 16:07               ` David Howells
2007-05-02  2:18                 ` Eric W. Biederman
2007-05-02  9:32                   ` David Howells
2007-05-02 11:55                     ` Eric W. Biederman
2007-05-02 12:05                       ` David Howells
2007-05-01 20:12               ` Satyam Sharma
2007-05-01 15:05             ` Randy Dunlap
2007-05-01 15:06               ` David Woodhouse
2007-05-01 20:44                 ` Satyam Sharma
2007-05-01 15:07             ` Geert Uytterhoeven
2007-05-01 15:11               ` David Woodhouse
2007-05-01 16:15         ` Stuart MacDonald
2007-04-30 21:34       ` Luck, Tony

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=20070430093331.GB11345@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.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;
as well as URLs for NNTP newsgroup(s).