From: Dave McCracken <dmccr@us.ibm.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>,
Magnus Damm <magnus.damm@gmail.com>
Cc: 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 13:23:58 -0500 [thread overview]
Message-ID: <BD6BD4B5349C1A151BF41FDF@[10.1.1.4]> (raw)
In-Reply-To: <44506023.4060609@yahoo.com.au>
--On Thursday, April 27, 2006 16:09:39 +1000 Nick Piggin
<nickpiggin@yahoo.com.au> wrote:
> Magnus Damm wrote:
>> On 4/11/06, Dave McCracken <dmccr@us.ibm.com> wrote:
>
>>> 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?
>
> Don't think there would be any objections. If someone sends
> along a broken out patch, I'm sure it could get into 2.6.18.
This patch is broken out. It only contains the changes necessary to
standardize the pxd_page/pxd_page_kernel macros across the architectures.
As far as I know the only reason it isn't being considered for merge is
that no one other than shared page tables has been using the macros.
Dave McCracken
--
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>
prev parent reply other threads:[~2006-04-27 18:23 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
2006-04-27 6:09 ` Nick Piggin
2006-04-27 18:23 ` Dave McCracken [this message]
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='BD6BD4B5349C1A151BF41FDF@[10.1.1.4]' \
--to=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=magnus.damm@gmail.com \
--cc=nickpiggin@yahoo.com.au \
/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