From: "Magnus Damm" <magnus.damm@gmail.com>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: Dave Hansen <haveblue@us.ibm.com>,
Hugh Dickins <hugh@veritas.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [RFC/PATCH] Shared Page Tables [1/2]
Date: Thu, 27 Apr 2006 12:49:49 +0900 [thread overview]
Message-ID: <aec7e5c30604262049v3ae18915le415ee33b2f80fc4@mail.gmail.com> (raw)
In-Reply-To: <C7A8E6F316A73810A5FF466E@10.1.1.4>
On 4/11/06, Dave McCracken <dmccr@us.ibm.com> wrote:
> --On Monday, April 10, 2006 11:54:56 -0700 Dave Hansen
> <haveblue@us.ibm.com> wrote:
>
> >> Complete the macro definitions for pxd_page/pxd_page_kernel
> >
> > Could you explain a bit why these are needed for shared page tables?
>
> The existing definitions define pte_page and pmd_page to return the struct
> page for the pfn contained in that entry, and pmd_page_kernel returns the
> kernel virtual address of it. However, pud_page and pgd_page are defined
> to return the kernel virtual address. There are no macros that return the
> struct page.
>
> No one actually uses any of the pud_page and pgd_page macros (other than
> one reference in the same include file). After some discussion on the list
> the last time I posted the patches, we agreed that changing pud_page and
> pgd_page to be consistent with pmd_page is the best solution. We also
> agreed that I should go ahead and propagate that change across all
> architectures even though not all of them currently support shared page
> tables. This patch is the result of that work.
What is the merge status of this patch?
I've written some generic page table creation code for kexec, but the
fact that pud_page() returns struct page * on i386 but unsigned long
on other architectures makes it hard to write clean generic code.
Any merge objections, or was this patch simply overlooked?
/ magnus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-04-27 3:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 16:13 Dave McCracken
2006-04-10 18:54 ` Dave Hansen
2006-04-10 19:05 ` Dave McCracken
[not found] ` <C7A8E6F316A73810A5FF466E@10.1.1.4>
2006-04-27 3:49 ` Magnus Damm [this message]
2006-04-27 6:09 ` Nick Piggin
2006-04-27 18:23 ` Dave McCracken
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=aec7e5c30604262049v3ae18915le415ee33b2f80fc4@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=dmccr@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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