From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Siva Prasad <sprasad@bivio.net>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: PTE entries
Date: Tue, 24 Apr 2007 11:05:00 +1000 [thread overview]
Message-ID: <1177376700.14873.40.camel@localhost.localdomain> (raw)
In-Reply-To: <D83235F0F3C86D4D889D8B9A0DA8C6D762C6C3@corpexc01.corp.networkrobots.com>
On Thu, 2007-04-19 at 21:34 -0700, Siva Prasad wrote:
> Hi,
>
>
>
> Where exactly the PTE are setup for any given new user program?
>
>
>
> In other words, if you are trying to execute a user level program,
> kernel needs to load it and setup PTEs for that program. Where does
> kernel do it?
They are faulted in.
See do_page_fault
Ben.
next prev parent reply other threads:[~2007-04-24 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 4:34 PTE entries Siva Prasad
2007-04-24 1:05 ` Benjamin Herrenschmidt [this message]
2007-04-25 3:34 ` Siva Prasad
2007-04-25 3:50 ` Benjamin Herrenschmidt
2007-05-02 19:58 ` Siva Prasad
2007-05-02 22:03 ` Paul Mackerras
2007-05-02 22:12 ` Benjamin Herrenschmidt
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=1177376700.14873.40.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sprasad@bivio.net \
/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;
as well as URLs for NNTP newsgroup(s).