From: Michael Ellerman <michael@ellerman.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] [POWERPC] Free a PTE bit on ppc64 with 64K pages
Date: Tue, 10 Jun 2008 14:00:51 +1000 [thread overview]
Message-ID: <1213070451.7957.3.camel@localhost> (raw)
In-Reply-To: <20080529055401.9B758DDDE7@ozlabs.org>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Thu, 2008-05-29 at 15:51 +1000, Benjamin Herrenschmidt wrote:
> This patch frees a PTE bit when using 64K pages on ppc64. This is done
> by getting rid of the separate _PAGE_HASHPTE bit. Instead, we just test
> if any of the 16 sub-page bits is set. For non-combo pages (ie. real
> 64K pages), we set SUB0 and the location encoding in that field.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> Please review and make sure I didn't miss something ...
This doesn't build for CONFIG_PPC_64K_PAGES=n and
CONFIG_PPC_HAS_HASH_64K=y, because the asm is protected by the latter
but the header definitions are protected by the former.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-06-10 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 5:51 [PATCH] [POWERPC] Free a PTE bit on ppc64 with 64K pages Benjamin Herrenschmidt
2008-06-10 4:00 ` Michael Ellerman [this message]
2008-06-10 6:50 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2008-06-11 5:37 [PATCH] powerpc: " Benjamin Herrenschmidt
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=1213070451.7957.3.camel@localhost \
--to=michael@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.