From: Nicholas Piggin <npiggin@gmail.com>
To: linux-mm@kvack.org
Cc: linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH 2/4] arm64: support huge vmap vmalloc
Date: Mon, 10 Jun 2019 14:38:36 +1000 [thread overview]
Message-ID: <20190610043838.27916-2-npiggin@gmail.com> (raw)
In-Reply-To: <20190610043838.27916-1-npiggin@gmail.com>
Applying huge vmap to vmalloc requires vmalloc_to_page to walk huge
pages. Define pud_large and pmd_large to support this.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
arch/arm64/include/asm/pgtable.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h
index 2c41b04708fe..30fe7b344bf7 100644
--- a/arch/arm64/include/asm/pgtable.h
+++ b/arch/arm64/include/asm/pgtable.h
@@ -428,6 +428,7 @@ extern pgprot_t phys_mem_access_prot(struct file *file, unsigned long pfn,
PMD_TYPE_TABLE)
#define pmd_sect(pmd) ((pmd_val(pmd) & PMD_TYPE_MASK) == \
PMD_TYPE_SECT)
+#define pmd_large(pmd) pmd_sect(pmd)
#if defined(CONFIG_ARM64_64K_PAGES) || CONFIG_PGTABLE_LEVELS < 3
#define pud_sect(pud) (0)
@@ -438,6 +439,7 @@ extern pgprot_t phys_mem_access_prot(struct file *file, unsigned long pfn,
#define pud_table(pud) ((pud_val(pud) & PUD_TYPE_MASK) == \
PUD_TYPE_TABLE)
#endif
+#define pud_large(pud) pud_sect(pud)
extern pgd_t init_pg_dir[PTRS_PER_PGD];
extern pgd_t init_pg_end[];
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-10 4:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 4:38 [PATCH 1/4] mm: Move ioremap page table mapping function to mm/ Nicholas Piggin
2019-06-10 4:38 ` Nicholas Piggin [this message]
2019-06-10 5:47 ` [PATCH 2/4] arm64: support huge vmap vmalloc Anshuman Khandual
2019-06-10 6:14 ` Nicholas Piggin
2019-06-10 4:38 ` [PATCH 3/4] powerpc/64s/radix: " Nicholas Piggin
2019-06-10 4:38 ` [PATCH 4/4] mm/vmalloc: Hugepage vmalloc mappings Nicholas Piggin
2019-06-10 5:49 ` Nicholas Piggin
2019-06-10 8:08 ` Satheesh Rajendran
2019-06-10 8:53 ` Anshuman Khandual
2019-06-11 0:16 ` Nicholas Piggin
2019-06-11 6:59 ` Anshuman Khandual
2019-06-19 3:29 ` Nicholas Piggin
2019-06-10 14:10 ` Mark Rutland
2019-06-10 14:44 ` Nicholas Piggin
2019-06-11 6:17 ` Anshuman Khandual
2019-06-19 3:33 ` Nicholas Piggin
2019-06-11 5:39 ` Christophe Leroy
2019-06-19 3:39 ` Nicholas Piggin
2019-06-10 5:42 ` [PATCH 1/4] mm: Move ioremap page table mapping function to mm/ Anshuman Khandual
2019-06-10 6:21 ` Nicholas Piggin
2019-06-11 5:24 ` Christophe Leroy
2019-06-19 3:43 ` Nicholas Piggin
2019-06-19 13:18 ` Christophe Leroy
2019-06-22 9:42 ` Nicholas Piggin
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=20190610043838.27916-2-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.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).