All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Renzo Davoli <renzo@cs.unibo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>,
	Ulrich Drepper <drepper@gmail.com>,
	osd@cs.unibo.it, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2-ptrace_multi
Date: Mon, 22 May 2006 11:26:08 -0400	[thread overview]
Message-ID: <20060522152608.GA21869@nevyn.them.org> (raw)
In-Reply-To: <20060522150544.GB11910@cs.unibo.it>

On Mon, May 22, 2006 at 05:05:44PM +0200, Renzo Davoli wrote:
> Then it would be inconsistent with ppc64 where it does exist, and ppc64
> has the very same problem.
> So the solution would be to patch also the ppc64 [GS]ETREGS breaking
> compatibility with existing applications. 

Or use new ptrace operations for the full regsets; that is probably
wiser.

> The MULTI proposal was a way to have a fast, simple, safe support.
> Fast: one syscall does all

You've added copy_from_user to several operations which were previously
entirely register-based calling conventions.  In at least some
configurations this will dwarf the cost of the system call trap.

> If you do not find this proposal interesting, I'll continue to support
> it as a specific patch for umview. I am not here to "sell" any solution.
> On the contrary I think it might be useful in many applications.

Well, I'm afraid that I don't find it interesting; and I don't think
GDB would make use of it.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-05-22 15:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 15:53 ptrace enhancements for VM support (patch proposals follow in sep.msgs) Renzo Davoli
2006-05-18 15:56 ` [PATCH] 1-access_process_vm_user Renzo Davoli
2006-05-18 15:58 ` [PATCH] 2-ptrace_multi Renzo Davoli
2006-05-18 20:17   ` Andi Kleen
2006-05-18 21:13     ` Renzo Davoli
2006-05-19  2:23       ` Ulrich Drepper
2006-05-19  9:07         ` Renzo Davoli
2006-05-19 13:09           ` Daniel Jacobowitz
2006-05-19 17:45             ` Renzo Davoli
2006-05-19 19:15               ` Renzo Davoli
2006-05-19 20:15               ` Daniel Jacobowitz
2006-05-19 20:17                 ` Andi Kleen
2006-05-20  6:44                   ` Ulrich Drepper
2006-05-20 14:37                   ` Alan Cox
2006-05-20 18:30                     ` Renzo Davoli
2006-05-20 20:23                       ` Ulrich Drepper
2006-05-20 21:39                       ` Jeff Dike
2006-05-21 12:38                         ` Avi Kivity
2006-05-21 15:28                         ` Renzo Davoli
2006-05-22 13:02                           ` Daniel Jacobowitz
2006-05-22 15:05                             ` Renzo Davoli
2006-05-22 15:26                               ` Daniel Jacobowitz [this message]
2006-05-18 16:07 ` [PATCH] 3-ptrace_vm Renzo Davoli
2006-05-21  8:03 ` ptrace enhancements for VM support (patch proposals follow in sep.msgs) Peter Chubb

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=20060522152608.GA21869@nevyn.them.org \
    --to=dan@debian.org \
    --cc=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=drepper@gmail.com \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osd@cs.unibo.it \
    --cc=renzo@cs.unibo.it \
    /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.