From: Gilles Pokam <gpokam@gmail.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel memory
Date: Thu, 28 Apr 2005 23:45:40 -0700 [thread overview]
Message-ID: <ba83582205042823452a3446f6@mail.gmail.com> (raw)
In-Reply-To: <20050429061254.GB12654@taniwha.stupidest.org>
On 4/28/05, Chris Wedgwood <cw@f00f.org> wrote:
> On Thu, Apr 28, 2005 at 10:48:31PM -0700, Gilles Pokam wrote:
>
> > Can you be more explicit ?
>
> why can't you have the parent process of whatever your tracing mess
> with /dev/kmem or whatever so you don't have to frob the original
> binary?
I see the point. Just to test this solution, I tried before to modify
a test application by mmaping /dev/mem into the application address
range. Since I don't know apriori which address is going to raise a
pagefault, I had to mmap the entire memory to the user space. However
this doesn't work. It looks like there is a limitation on the amount
of memory you can mmap ?
> i guess it's not really clear to me what you're doing entirely
the simplest way to say is: I want the pagefault handler to return a
memory page when it encounters a pagefault exceptions due to an
invalid address or incorrect page protection.
Thanks.
Gilles
next prev parent reply other threads:[~2005-04-29 6:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 23:52 Kernel memory Gilles Pokam
2005-04-29 3:03 ` Chris Wedgwood
2005-04-29 5:33 ` Gilles Pokam
2005-04-29 5:43 ` Chris Wedgwood
2005-04-29 5:48 ` Gilles Pokam
2005-04-29 6:12 ` Chris Wedgwood
2005-04-29 6:45 ` Gilles Pokam [this message]
2005-04-29 6:48 ` Chris Wedgwood
2005-04-29 7:12 ` Gilles Pokam
-- strict thread matches above, loose matches on Subject: below --
2012-06-21 12:27 Kernel Memory Vijay Chauhan
2012-06-21 13:35 ` HowKernel StuffWorks
2012-06-21 13:40 ` kishore sheik ahamed
2012-06-22 18:23 ` Vijay Chauhan
2012-06-21 13:44 ` Arun KS
2012-06-21 14:02 ` AFT
2012-06-21 15:48 ` michi1 at michaelblizek.twilightparadox.com
2016-05-17 7:11 Kernel memory Ronit Halder
2016-05-17 15:05 ` Valdis.Kletnieks at vt.edu
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=ba83582205042823452a3446f6@mail.gmail.com \
--to=gpokam@gmail.com \
--cc=cw@f00f.org \
--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.