From: Ralf Baechle <ralf@linux-mips.org>
To: Harald Krapfenbauer <krapfenbauer@ict.tuwien.ac.at>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: ptrace question
Date: Mon, 14 Jul 2008 12:43:42 +0100 [thread overview]
Message-ID: <20080714114342.GE10379@linux-mips.org> (raw)
In-Reply-To: <487B3242.60202@ict.tuwien.ac.at>
On Mon, Jul 14, 2008 at 01:02:26PM +0200, Harald Krapfenbauer wrote:
> Hello,
>
> If I write memory (maybe with instructions) of a traced application with
> the ptrace() call, are the caches invalidated automatically, i.e. can I
> assume that the processor uses the newly written values after continuing?
ptrace semantics requires PTRACE_POKETEXT to ensure I-cache coherency and
consistency.
Ralf
next prev parent reply other threads:[~2008-07-14 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 11:02 ptrace question Harald Krapfenbauer
2008-07-14 11:43 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-17 16:23 Rajeev Bector
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=20080714114342.GE10379@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=krapfenbauer@ict.tuwien.ac.at \
--cc=linux-mips@linux-mips.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.