LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de> To: linux-kernel@vger.kernel.org Subject: [PATCH] [4/8] GBPAGES: Add pgtable accessor functions for GB pages Date: Thu, 3 Jan 2008 18:27:00 +0100 (CET) [thread overview] Message-ID: <20080103172700.E284514DDD@wotan.suse.de> (raw) In-Reply-To: <20080103626.635376000@suse.de> Signed-off-by: Andi Kleen <ak@suse.de> --- include/asm-x86/pgtable_64.h | 3 +++ 1 file changed, 3 insertions(+) Index: linux/include/asm-x86/pgtable_64.h =================================================================== --- linux.orig/include/asm-x86/pgtable_64.h +++ linux/include/asm-x86/pgtable_64.h @@ -320,6 +320,9 @@ static inline int pmd_large(pmd_t pte) { return (pmd_val(pte) & __LARGE_PTE) == __LARGE_PTE; } +static inline int pud_large(pud_t pte) { + return (pud_val(pte) & __LARGE_PTE) == __LARGE_PTE; +} /* * Conversion functions: convert a page and protection to a page entry,
next prev parent reply other threads:[~2008-01-03 17:28 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-03 17:26 [PATCH] [0/8] GB pages (PDP1GB) support for the kernel direct mapping Andi Kleen 2008-01-03 17:26 ` [PATCH] [1/8] GBPAGES: Handle kernel near memory hole in clear_kernel_mapping Andi Kleen 2008-01-03 18:29 ` Vivek Goyal 2008-01-03 18:43 ` Andi Kleen 2008-01-03 17:26 ` [PATCH] [2/8] GBPAGES: Add feature macros for the gbpages cpuid bit Andi Kleen 2008-01-03 17:26 ` [PATCH] [3/8] GBPAGES: Split LARGE_PAGE_SIZE/MASK into PUD_PAGE_SIZE/PMD_PAGE_SIZE Andi Kleen 2008-01-03 17:27 ` Andi Kleen [this message] 2008-01-03 17:27 ` [PATCH] [5/8] GBPAGES: Support gbpages in pagetable dump Andi Kleen 2008-01-03 17:27 ` [PATCH] [6/8] GBPAGES: Add an option to disable direct mapping gbpages and a global variable Andi Kleen 2008-01-03 19:03 ` Nish Aravamudan 2008-01-03 17:27 ` [PATCH] [7/8] GBPAGES: Implement GBpages support in change_page_attr() Andi Kleen 2008-01-03 17:27 ` [PATCH] [8/8] GBPAGES: Do kernel direct mapping at boot using GB pages Andi Kleen
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=20080103172700.E284514DDD@wotan.suse.de \ --to=ak@suse.de \ --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: linkBe 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).