linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: benh@kernel.crashing.org, paulus@samba.org, dwg@au1.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: [PATCH -V8 02/18] mm/THP: Use pmd_populate to update the pmd with pgtable_t pointer
Date: Sun, 12 May 2013 21:44:09 +0530	[thread overview]
Message-ID: <1368375265-19593-3-git-send-email-aneesh.kumar@linux.vnet.ibm.com> (raw)
In-Reply-To: <1368375265-19593-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>

We should not use set_pmd_at to update pmd_t with pgtable_t pointer. set_pmd_at
is used to set pmd with huge pte entries and architectures like ppc64, clear
few flags from the pte when saving a new entry. Without this change we observe
bad pte errors like below on ppc64 with THP enabled.

BUG: Bad page map in process ld mm=0xc000001ee39f4780 pte:7fc3f37848000001 pmd:c000001ec0000000
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
---
 mm/huge_memory.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 03a89a2..49cb001 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -2325,7 +2325,7 @@ static void collapse_huge_page(struct mm_struct *mm,
 		pte_unmap(pte);
 		spin_lock(&mm->page_table_lock);
 		BUG_ON(!pmd_none(*pmd));
-		set_pmd_at(mm, address, pmd, _pmd);
+		pmd_populate(mm, pmd, _pmd);
 		spin_unlock(&mm->page_table_lock);
 		anon_vma_unlock_write(vma->anon_vma);
 		goto out;
-- 
1.8.1.2

  parent reply	other threads:[~2013-05-12 16:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12 16:14 [PATCH -V8 00/18] THP support for PPC64 Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 01/18] powerpc/mm: Use the correct mask value when looking at pgtable address Aneesh Kumar K.V
2013-05-12 16:14 ` Aneesh Kumar K.V [this message]
2013-05-12 16:14 ` [PATCH -V8 03/18] mm/THP: Use the right function when updating access flags Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 04/18] mm/THP: Add pmd args to pgtable deposit and withdraw APIs Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 05/18] mm/THP: withdraw the pgtable after pmdp related operations Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 06/18] mm/THP: Don't use HPAGE_SHIFT in transparent hugepage code Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 07/18] mm/THP: deposit the transpare huge pgtable before set_pmd Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 08/18] powerpc/THP: Double the PMD table size for THP Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 09/18] powerpc/THP: Implement transparent hugepages for ppc64 Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 10/18] powerpc: move find_linux_pte_or_hugepte and gup_hugepte to common code Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 11/18] powerpc: Update find_linux_pte_or_hugepte to handle transparent hugepages Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 12/18] powerpc: Replace find_linux_pte with find_linux_pte_or_hugepte Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 13/18] powerpc: Update gup_pmd_range to handle transparent hugepages Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 14/18] powerpc/THP: Add code to handle HPTE faults for hugepages Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 15/18] powerpc: Make linux pagetable walk safe with THP enabled Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 16/18] powerpc/THP: Enable THP on PPC64 Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 17/18] powerpc: Optimize hugepage invalidate Aneesh Kumar K.V
2013-05-12 16:14 ` [PATCH -V8 18/18] powerpc: disable assert_pte_locked for collapse_huge_page Aneesh Kumar K.V

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=1368375265-19593-3-git-send-email-aneesh.kumar@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=dwg@au1.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).