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

Hi Benjamin,
Benjamin Herrenschmidt 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 :-)
>   

Because we want full PTE table for PKMAP with 4K pages (it's pretty
small - only 512 pages so we really want to use all). And as current
code doesn't support PKMAP being in different PTE tables we want to
align to full PTE table not to lost part of it.

>>  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.
>   

Well. But pte_t/pgd_t are actually in page.h not page_32.h (along with
pmd/pud for 64bit)... So maybe we need to put definitions for
PMD_T_LOG2/PUD_T_LOG2 too...

Regards, Ilya.

  reply	other threads:[~2008-12-11  1:52 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
2008-12-11  1:51       ` Ilya Yanok [this message]
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=49407234.7070501@emcraft.com \
    --to=yanok@emcraft.com \
    --cc=benh@kernel.crashing.org \
    --cc=dzu@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=pvr@emcraft.com \
    --cc=wd@denx.de \
    /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).