From: Andi Kleen <ak@suse.de>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
akpm@digeo.com
Subject: Re: 4level page tables for Linux
Date: Tue, 12 Oct 2004 21:03:46 +0200 [thread overview]
Message-ID: <20041012190346.GA705@wotan.suse.de> (raw)
In-Reply-To: <1097606902.10652.203.camel@localhost>
On Tue, Oct 12, 2004 at 11:48:22AM -0700, Dave Hansen wrote:
> @@ -110,13 +115,18 @@ int install_file_pte(struct mm_struct *m
> unsigned long addr, unsigned long pgoff, pgprot_t prot)
> {
> ...
> + pml4 = pml4_offset(mm, addr);
> +
> + spin_lock(&mm->page_table_lock);
> + pgd = pgd_alloc(mm, pml4, addr);
> + if (!pgd)
> + goto err_unlock;
>
> Locking isn't needed for access to the pml4? This is a wee bit
> different from pgd's and I didn't see any documentation about it
> anywhere. Could be confusing.
No, the lock is still needed. Thanks for catching this, that was indeed
wrong.
>
> +++ linux-2.6.9rc4-4level/mm/memory.c
> ...
> +#undef inline
> +#define inline
> +unsigned long caddr;
>
> Is this just for debugging?
Yes, that's a leftover I forgot to remove. Will go in the next
version.
(btw t here is another leftover in there, I will remove it too)
>
> +static inline void free_one_pml4(struct mmu_gather *tlb, pml4_t *pml4,
> + unsigned long addr, unsigned long end)
> +{
> ...
> + do {
> + caddr = addr;
> + free_one_pgd(tlb, pgd);
> + free++;
> + addr = (addr + PGDIR_SIZE) & PGDIR_MASK;
> + pgd++;
> + } while (addr && addr < end);
>
> If someone attempts to clear an address which is in the top PGDIR_SIZE
> bytes of memory, this will overflow. Is that an issue?
That is what the addr && is for. Yes, overflows happen and afaik they
are all handled.
>
> There also seems to be quite a bit of churn in the copy_*_range()
> functions that isn't completely related to the pml4 changes. Should
> that get broken out?
It's related. The old function just wasn't scalable to 4 level
page tables at all (i really tried but it was too ugly) so I rewrote it
completely. Splitting it would be difficult because the 3level version
would be already very different from the 4level version.
Thanks for the review.
-Andi
next prev parent reply other threads:[~2004-10-12 19:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 13:59 4level page tables for Linux Andi Kleen
2004-10-12 18:48 ` Dave Hansen
2004-10-12 19:03 ` Andi Kleen [this message]
2004-10-12 19:08 ` 4level page tables for Linux II Andi Kleen
2004-10-13 18:41 ` 4level page tables for Linux Andrea Arcangeli
2004-10-13 19:35 ` Andi Kleen
2004-10-13 20:04 ` Andrea Arcangeli
2004-10-18 17:02 ` Christoph Lameter
2004-10-18 17:21 ` Andi Kleen
2004-10-18 17:38 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2004-10-13 23:22 Albert Cahalan
2004-10-13 23:51 ` Andrea Arcangeli
2004-10-14 1:15 ` Albert Cahalan
2004-10-14 9:25 linux
2004-10-14 11:15 ` Robin Holt
2004-10-17 2:57 ` H. Peter Anvin
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=20041012190346.GA705@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@digeo.com \
--cc=haveblue@us.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox