linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Yuri Tikhonov <yur@emcraft.com>
Cc: linuxppc-dev@ozlabs.org, Vladimir Panfilov <pvr@emcraft.com>,
	dzu@denx.de, Ilya Yanok <yanok@emcraft.com>,
	wd@denx.de
Subject: Re: Re[2]: [PATCH] powerpc: add 16K/64K pages support for the 44x PPC32 architectures.
Date: Thu, 11 Dec 2008 06:58:21 +1100	[thread overview]
Message-ID: <1228939101.22413.69.camel@pasglop> (raw)
In-Reply-To: <1251410626.20081210142142@emcraft.com>

On Wed, 2008-12-10 at 14:21 +0300, Yuri Tikhonov wrote:
> 
> > I'm not sure about the above & PMD_MASK. Shouldn't we instead make it
> > not build if (PKMAP_BASE & PMD_MASK) != 0 ? 
> 
>  We separated the !4K_PAGES case here exactly because  (PKMAP_BASE & 
> PMD_MASK) != 0 [see the comment to this chunk - why]. So, this'll turn 
> out to be broken if we follow your suggestion. Are there any reasons 
> why we should have PKMAP_BASE aligned on the PMD_SIZE boundary ?

No, you are right, so why do we need the & PMD_MASK in the 4k case ?

What I don't get is why do we need a different formula for 4k and 64k
but I might just be stupid :-)

>  These definitions seem to be related to the page table, so, as for me, 
> then pgtable.h is the better place for them. Though, as you want; 
> we'll move this to page_32.h.

Well, I like having them next to the pte_t/pgd_t definitions since they
relate directly to the size of those structures.

Cheers,
Ben.

  reply	other threads:[~2008-12-10 19:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 23:44 [PATCH] powerpc: add 16K/64K pages support for the 44x PPC32 architectures Ilya Yanok
2008-12-01 23:06 ` Hollis Blanchard
2008-12-01 23:22   ` Josh Boyer
2008-12-02  0:09   ` Benjamin Herrenschmidt
2008-12-09 21:39 ` Benjamin Herrenschmidt
2008-12-10 11:21   ` Re[2]: " Yuri Tikhonov
2008-12-10 19:58     ` Benjamin Herrenschmidt [this message]
2008-12-11  1:51       ` Ilya Yanok
2008-12-10 13:58   ` Ilya Yanok
2008-12-11  1:39     ` Ilya Yanok
2008-12-11  1:55       ` Ilya Yanok
2008-12-17 19:56         ` Josh Boyer
2008-12-24 17:03           ` Josh Boyer
2008-12-26 21:22             ` Benjamin Herrenschmidt
2008-12-27 12:05               ` Josh Boyer

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=1228939101.22413.69.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=dzu@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=pvr@emcraft.com \
    --cc=wd@denx.de \
    --cc=yanok@emcraft.com \
    --cc=yur@emcraft.com \
    /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).