From: mnm.kernel@gmail.com (Manavendra Nath Manav)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Page fault in kernel code
Date: Wed, 10 Sep 2014 14:45:23 +0530 [thread overview]
Message-ID: <CAJKgH8Dx1CStuWvgWXyrHEXA8LEDMv9PAZWNDph2AvQ=7owXTQ@mail.gmail.com> (raw)
In-Reply-To: <4E5779AD88B2F040B8A7E83ECF544D1A55B65C@SJCPEX01CL02.citrite.net>
On 09-Sep-2014 10:25 pm, "Jeff Haran" <Jeff.Haran@citrix.com> wrote:
>
>
> While reading the book Essential Linux device drivers it says "user mode
code is allowed to page fault, however, whereas kernel mode code isn't".
>
> Why is it so? Why can't kernel mode code handle the page fault and reload
the page from swap? Also, can page fault occur when kernel is executing in
process context and/or interrupt context?
>
> -- manav m-n
>
> Think about handling the case where a page fault has occurred but the
code that handles the page fault is itself not already in RAM, which leads
to another page fault. Gets complicated. That complexity can be avoided by
keeping all the kernel code in RAM all the time. Same applies to the kernel
data that is needed to handle a page fault.
>
> Jeff Haran
>
>
But if the total RAM is limited (less than 896MB LOWMEM), for example as in
embedded devices how the kernel code be kept in RAM all the time. Am I
correct to assume that the kernel pre-fetches all pages when entering
kernel mode from user mode?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140910/eb2f31cd/attachment-0001.html
next prev parent reply other threads:[~2014-09-10 9:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJKgH8Df51ZL-BaN_zBmtP=2tjxh5po6KWdbR1Q7LwiR2DZzTg@mail.gmail.com>
2014-09-09 13:23 ` Page fault in kernel code Manavendra Nath Manav
2014-09-09 14:25 ` Greg KH
2014-09-09 15:51 ` Valdis.Kletnieks at vt.edu
2014-09-09 16:54 ` Jeff Haran
2014-09-10 9:15 ` Manavendra Nath Manav [this message]
2014-09-10 12:54 ` Valdis.Kletnieks at vt.edu
2014-09-10 14:52 ` Manavendra Nath Manav
2014-09-11 12:03 ` Leon Romanovsky
2014-09-11 14:19 ` Christoph Lameter
2014-09-11 14:53 ` Miles MH Chen
2014-09-11 15:26 ` Leon Romanovsky
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='CAJKgH8Dx1CStuWvgWXyrHEXA8LEDMv9PAZWNDph2AvQ=7owXTQ@mail.gmail.com' \
--to=mnm.kernel@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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.