From: Andrea Righi <righi.andrea@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mmotm] mm: unify some pmd_*() functions
Date: Tue, 10 Feb 2009 14:41:37 +0100 [thread overview]
Message-ID: <a2776ec50902100541p1503adaay52d221411d92c842@mail.gmail.com> (raw)
In-Reply-To: <16182.1234199195@redhat.com>
On Mon, Feb 9, 2009 at 6:06 PM, David Howells <dhowells@redhat.com> wrote:
> Andrea Righi <righi.andrea@gmail.com> wrote:
>
>> Unify all the identical implementations of pmd_free(), __pmd_free_tlb(),
>> pmd_alloc_one(), pmd_addr_end() in include/asm-generic/pgtable-nopmd.h
>
> NAK for FRV on two fronts:
This patch generates too many followup fixes and it's better to simply drop it
for now.
I think we need to use a different approach and, more important, we need to
clean a lot of .h files before to avoid the include hell problems.
-Andrea
>
> (1) The definition of pud_t in pgtable-nopud.h:
>
> typedef struct { pgd_t pgd; } pud_t;
>
> is not consistent with the one in FRV's page.h:
>
> typedef struct { unsigned long ste[64];} pmd_t;
> typedef struct { pmd_t pue[1]; } pud_t;
> typedef struct { pud_t pge[1]; } pgd_t;
>
> The upper intermediate page table is contained within the page directory
> entry, not the other way around. Having a pgd_t inside a pud_t is
> upside-down, illogical and makes things harder to follow IMNSHO.
>
> (2) It produces the following errors:
>
> mm/memory.c: In function 'free_pmd_range':
> mm/memory.c:176: error: implicit declaration of function '__pmd_free_tlb'
> CC fs/seq_file.o
> mm/memory.c: In function '__pmd_alloc':
> mm/memory.c:2896: error: implicit declaration of function 'pmd_alloc_one_bug'
> mm/memory.c:2896: warning: initialization makes pointer from integer without a cast
> mm/memory.c:2905: error: implicit declaration of function 'pmd_free'
>
> David
--
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:[~2009-02-10 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 21:35 [PATCH -mmotm] mm: unify some pmd_*() functions Andrea Righi
2009-01-25 21:39 ` Andrea Righi
2009-01-28 1:41 ` Andrew Morton
2009-01-28 17:59 ` Andrea Righi
2009-01-29 20:02 ` Geert Uytterhoeven
2009-02-09 17:06 ` David Howells
2009-02-10 13:41 ` Andrea Righi [this message]
2009-02-11 10:16 ` Martin Schwidefsky
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=a2776ec50902100541p1503adaay52d221411d92c842@mail.gmail.com \
--to=righi.andrea@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).