mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ulrich Drepper" <drepper@gmail.com>
To: "Renzo Davoli" <renzo@cs.unibo.it>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, "Andi Kleen" <ak@suse.de>,
	"Daniel Jacobowitz" <dan@debian.org>,
	osd@cs.unibo.it, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2-ptrace_multi
Date: Sat, 20 May 2006 13:23:24 -0700	[thread overview]
Message-ID: <a36005b50605201323u212158e3h6a8a6419f71efeba@mail.gmail.com> (raw)
In-Reply-To: <20060520183020.GC11648@cs.unibo.it>

On 5/20/06, Renzo Davoli <renzo@cs.unibo.it> wrote:
> Let me point out that PTRACE_MULTI is not only related to memory access.

You've already been told that syscalls are very fast.  For any small
number of calls the overhead is neglectable.  Only for possibly huge
numbers of calls (like those needed to transfer memory content) is the
overhead significant but that is irrelevant because of /proc/*/mem.

Whatever other problems you have (accessing multiple registers) is an
arch-specific problem.  If this is a real problem talk to the arch
maintainer about adding a call to get all registers at once.  This is
nothing which should be handled with a construct like hte
PTRACE_MULTI.

  reply	other threads:[~2006-05-20 20:23 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 [this message]
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
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=a36005b50605201323u212158e3h6a8a6419f71efeba@mail.gmail.com \
    --to=drepper@gmail.com \
    --cc=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dan@debian.org \
    --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 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®