From: Gilles Pokam <gpokam@gmail.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel memory
Date: Fri, 29 Apr 2005 00:12:43 -0700 [thread overview]
Message-ID: <ba835822050429001234304bd1@mail.gmail.com> (raw)
In-Reply-To: <20050429064819.GA15501@taniwha.stupidest.org>
On 4/28/05, Chris Wedgwood <cw@f00f.org> wrote:
> On Thu, Apr 28, 2005 at 11:45:40PM -0700, Gilles Pokam wrote:
>
> > 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.
>
> where should this page come from?
One way is to make the pagefault handler return a new vma that
contains the faulty address when such a scenario is encountered. The
normal pagefault mechanism will then apply by the time that address
gets accessed again since the address will now be valid. So a page
will be allocated. But I don't know how what should be changed in the
kernel to enable this behavior.
next prev parent reply other threads:[~2005-04-29 7:12 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
2005-04-29 6:48 ` Chris Wedgwood
2005-04-29 7:12 ` Gilles Pokam [this message]
-- 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=ba835822050429001234304bd1@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.