From: William Lee Irwin III <wli@holomorphy.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>, linux-mm@kvack.org
Subject: Re: [PATCH] remove unnecessary PAE pgd set
Date: Wed, 30 Apr 2003 20:45:51 -0700 [thread overview]
Message-ID: <20030501034551.GB20911@holomorphy.com> (raw)
In-Reply-To: <3EB096D8.80905@us.ibm.com>
William Lee Irwin III wrote:
>> I suspect this set_pgd() should go away for non-PAE also.
On Wed, Apr 30, 2003 at 08:39:04PM -0700, Dave Hansen wrote:
> Wouldn't it be analogous to the PMD set with PAE on, and necessary?
> Since processes don't share PGDs in 4G mode, the PGD entry could be
> missing in a process's pagetables after the kernel ones have been filled
> in. That set_pgd() will be necessary to move any new entry over.
Not really; it should just fall through to the pmd "level", which as
emulated should do all the instantiation needed for non-PAE.
On Wed, Apr 30, 2003 at 08:39:04PM -0700, Dave Hansen wrote:
> - a process does a vmalloc, which eventually calls pte_alloc_kernel()
> - pte_alloc_kernel() is always called with init_mm as its mm argument
> - pte_alloc_kernel() populates init_mm PGD entries with the new pte page
> - the process goes to use its new vmalloc'd area, and faults, because
> its pgd doesn't have the same entries. do_page_fault():vmalloc_fault
> brings over the necessary entries from init, and the fault is handled
Sounds like a good plan to me.
On Wed, Apr 30, 2003 at 08:39:04PM -0700, Dave Hansen wrote:
> The other option is to hold mmlist_lock and populate the entries around
> when pte_alloc_kernel() is called. The lazy way is better because not
> every process will go looking into the vmalloc area, _and_ and new pgds
> should be copied from the init one anyway, and inherit the PTE mapping.
> The lazy update only needs to be done for processes when their PGDs
> were allocated in the past.
Yeah, that could get ugly. Best to keep things lazy.
-- wli
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2003-05-01 3:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 23:42 Dave Hansen
2003-05-01 3:22 ` William Lee Irwin III
2003-05-01 3:39 ` Dave Hansen
2003-05-01 3:45 ` William Lee Irwin III [this message]
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=20030501034551.GB20911@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox