From: Daniel Jacobowitz <dan@debian.org>
To: fcorneli@elis.rug.ac.be
Cc: linux-kernel@vger.kernel.org, Frank.Cornelis@elis.rug.ac.be
Subject: Re: [PATCH] ptrace PTRACE_READDATA/WRITEDATA, kernel 2.5.62
Date: Mon, 24 Feb 2003 09:16:08 -0500 [thread overview]
Message-ID: <20030224141608.GA24699@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302241448140.1277-100000@tom.elis.rug.ac.be>
On Mon, Feb 24, 2003 at 03:05:14PM +0100, fcorneli@elis.rug.ac.be wrote:
> Hi,
>
> I ported some generic SunOS ptrace requests from my 2.4 exptrace kernel
> patch to the 2.5 tree. The PTRACE_READDATA/WRITEDATA requests have been
> available for a long time for the sparc architecture but I think they're
> also very useful on the i386 arch since PTRACE_PEEKDATA/POKEDATA are way
> too slow when handling large data blocks.
FYI Frank, three things. First of all, I really don't like the
interface of adding a second address to ptrace; I believe it interferes
with PIC on x86, since IIRC the extra argument would go in %ebx. The
BSDs have a nice interface involving passing a request structure.
Secondly, the implementation should be in kernel/ptrace.c not under
i386, we're trying to stop doing that.
Thirdly, I was going to do this, but I ended up making GDB use pread64
on /dev/mem instead. It works with no kernel modifications, and is
just as fast.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-24 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 14:05 [PATCH] ptrace PTRACE_READDATA/WRITEDATA, kernel 2.5.62 fcorneli
2003-02-24 14:16 ` Daniel Jacobowitz [this message]
2003-02-24 14:51 ` fcorneli
2003-02-24 15:02 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 18:21 Manfred Spraul
2003-02-25 10:36 ` fcorneli
2003-02-25 17:35 ` Manfred Spraul
2003-02-25 21:36 ` Andrew Morton
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=20030224141608.GA24699@nevyn.them.org \
--to=dan@debian.org \
--cc=Frank.Cornelis@elis.rug.ac.be \
--cc=fcorneli@elis.rug.ac.be \
--cc=linux-kernel@vger.kernel.org \
/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.