From: Keith Owens <kaos@melbourne.sgi.com>
To: "Siders, Keith" <keith_siders@toshibatv.com>
Cc: "Linux-Mips (E-mail)" <linux-mips@oss.sgi.com>
Subject: Re: Memory mapping
Date: Tue, 20 Nov 2001 11:15:04 +1100 [thread overview]
Message-ID: <9740.1006215304@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 19 Nov 2001 10:18:23 MDT." <7DF7BFDC95ECD411B4010090278A44CA1B743F@ATVX>
On Mon, 19 Nov 2001 10:18:23 -0600,
"Siders, Keith" <keith_siders@toshibatv.com> wrote:
>OK, now that I've spent a couple weeks looking at Linux memory management,
>can someone please help me straighten this out. First, I have a requirement
>to "unobtrusively" hot-patch instruction code ( and probably data also )
>segments in memory.
At the risk of stating the obvious, have you looked at the ptrace code
in arch/$(ARCH)/kernel/ptrace.c? That already does all the work for
reading and writing code and data.
next prev parent reply other threads:[~2001-11-20 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 16:18 Memory mapping Siders, Keith
2001-11-20 0:15 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 15:32 Siders, Keith
2004-12-17 4:54 memory mapping Srividya Ramanathan
2005-05-16 19:55 Xeno-unstable crashing at boot Ian Pratt
2005-05-17 11:52 ` Mike Wray
2005-05-17 13:26 ` Keir Fraser
2005-05-17 16:01 ` memory mapping Grzegorz Milos
2005-05-17 16:09 ` Grzegorz Milos
2009-02-16 16:58 Memory mapping Frederic Beck
2009-02-18 14:35 ` Frederic Beck
2011-05-06 14:50 Memory Mapping Lakshitha Harshan
2011-05-06 15:31 ` Konrad Rzeszutek Wilk
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=9740.1006215304@kao2.melbourne.sgi.com \
--to=kaos@melbourne.sgi.com \
--cc=keith_siders@toshibatv.com \
--cc=linux-mips@oss.sgi.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 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.