From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'David Gibson' <david@gibson.dropbear.id.au>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: IA64 non-contiguous memory space bugs
Date: Wed, 22 Feb 2006 02:45:27 +0000 [thread overview]
Message-ID: <200602220245.k1M2jRg10282@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060222022558.GE23574@localhost.localdomain>
In-Reply-To: <20060222001359.GA23574@localhost.localdomain>
David Gibson wrote on Tuesday, February 21, 2006 6:26 PM
> Chen, Kenneth W wrote on Tuesday, February 21, 2006 5:32 PM
> > free_pgtables() has partial crap that the check of is_hugepage_only_range()
> > should be done on the entire vma range, not just the first hugetlb page.
> > Though, it's not possible to have a hugetlb vma while having normal page
> > instantiated inside that vma. So the bug is mostly phantom. For
> > correctness, it should be fixed.
>
> Actually, from ppc64's point of view, the problem with the test is
> that the whole vma could be *less* than HPAGE_SIZE - we don't test
> that the address is aligned before checking is_hugepage_only_range().
> We thus can call hugetlb_free_pgd_range() on normal page VMAs - which
> we only get away with because the ppc64 hugetlb_free_pgd_range() is
> (so far) an alias for the normal free_pgd_range().
>
> Your patch below is insufficient, because there's a second test of
> is_hugepage_only_range() further down. However, instead of tweaking
> the tested ranges, I think what we really want to do is check for
> is_vm_hugetlb_page() instead.
>
> I was worried before, but now that you point out it's the 'end'
> address which really matters, not the ceiling, that might be
> sufficient. Um.. except that hugepages, unlike normal pages these
> days don't necessarily clean up all possible pagetable pages on
> unmap... crud. Still the patch below ought to be an improvement.
I agree. It's an improvement with your patch.
For ia64:
Acked-by: Ken Chen <kenneth.w.chen@intel.com>
> Index: working-2.6/mm/memory.c
> =================================> --- working-2.6.orig/mm/memory.c 2006-02-22 10:42:14.000000000 +1100
> +++ working-2.6/mm/memory.c 2006-02-22 13:22:07.000000000 +1100
> @@ -277,7 +277,7 @@ void free_pgtables(struct mmu_gather **t
> anon_vma_unlink(vma);
> unlink_file_vma(vma);
>
> - if (is_hugepage_only_range(vma->vm_mm, addr, HPAGE_SIZE)) {
> + if (is_vm_hugetlb_page(vma)) {
> hugetlb_free_pgd_range(tlb, addr, vma->vm_end,
> floor, next? next->vm_start: ceiling);
> } else {
> @@ -285,8 +285,7 @@ void free_pgtables(struct mmu_gather **t
> * Optimization: gather nearby vmas into one call down
> */
> while (next && next->vm_start <= vma->vm_end + PMD_SIZE
> - && !is_hugepage_only_range(vma->vm_mm, next->vm_start,
> - HPAGE_SIZE)) {
> + && !is_vm_hugetlb_page(vma->vm_mm)) {
> vma = next;
> next = vma->vm_next;
> anon_vma_unlink(vma);
next prev parent reply other threads:[~2006-02-22 2:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 0:13 IA64 non-contiguous memory space bugs David Gibson
2006-02-22 0:39 ` David S. Miller
2006-02-22 2:17 ` David Gibson
2006-02-22 1:31 ` Chen, Kenneth W
2006-02-22 2:15 ` 'David Gibson'
2006-02-22 1:51 ` Chen, Kenneth W
2006-02-22 2:25 ` 'David Gibson'
2006-02-22 16:35 ` Hugh Dickins
2006-02-22 23:49 ` 'David Gibson'
2006-02-23 20:13 ` Hugh Dickins
2006-02-24 0:11 ` 'David Gibson'
2006-02-22 2:45 ` Chen, Kenneth W [this message]
2006-02-22 2:53 ` Chen, Kenneth W
2006-02-22 3:55 ` David Mosberger-Tang
2006-02-22 4:02 ` David Gibson
2006-02-22 3:01 ` Zhang, Yanmin
2006-02-22 16:19 ` Chen, Kenneth W
2006-02-22 23:26 ` 'David Gibson'
2006-02-24 1:14 ` Chen, Kenneth W
2006-02-24 2:46 ` 'David Gibson'
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=200602220245.k1M2jRg10282@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=david@gibson.dropbear.id.au \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox