From: Prasanna S Panchamukhi <prasanna@in.ibm.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
davem@davemloft.net, suparna@in.ibm.com,
richardj_moore@uk.ibm.com, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: RFC - Approaches to user-space probes
Date: Fri, 31 Mar 2006 17:25:29 +0530 [thread overview]
Message-ID: <20060331115529.GA3501@in.ibm.com> (raw)
In-Reply-To: <y0m64lye28w.fsf@ton.toronto.redhat.com>
On Tue, Mar 28, 2006 at 03:35:43PM -0500, Frank Ch. Eigler wrote:
> Prasanna S Panchamukhi <prasanna@in.ibm.com> writes:
>
> > [...]
> > If the executable is mmaped shared, then those mappings will get written
> > back to the disk.
> > Writting to the disk is not the requirement for user-space probes, it is
> > just the side effect [...]
>
> It's pretty clear that writing the dirtied pages to disk is an
> *undesirable* side-effect, and should be eliminated. (Among many
> other scenarios, imagine a kernel shutting down without all the probes
> being cleanly removed. Then the executables are irretrievably
> corrupted.)
Frank,
What would the tipical situations where the text section in the
executable is mapped with 'MAP_SHARED'?
This information will help solve the problem easily.
Thanks
Prasanna
--
Prasanna S Panchamukhi
Linux Technology Center
India Software Labs, IBM Bangalore
Email: prasanna@in.ibm.com
Ph: 91-80-51776329
next prev parent reply other threads:[~2006-03-31 11:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 6:54 RFC - Approaches to user-space probes Prasanna S Panchamukhi
2006-03-27 7:37 ` Arjan van de Ven
2006-03-27 10:00 ` Prasanna S Panchamukhi
2006-03-27 20:03 ` Arjan van de Ven
2006-03-28 9:42 ` Richard J Moore
2006-03-28 9:47 ` Andi Kleen
2006-03-28 10:10 ` Richard J Moore
2006-03-28 14:54 ` Prasanna S Panchamukhi
2006-03-28 17:29 ` Arjan van de Ven
2006-03-28 20:35 ` Frank Ch. Eigler
2006-03-28 20:44 ` Andi Kleen
2006-03-31 11:55 ` Prasanna S Panchamukhi [this message]
2006-03-31 16:25 ` Frank Ch. Eigler
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=20060331115529.GA3501@in.ibm.com \
--to=prasanna@in.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=fche@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=richardj_moore@uk.ibm.com \
--cc=suparna@in.ibm.com \
--cc=tytso@mit.edu \
/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