From: Scott Wood <scottwood@freescale.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
<linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
"Joakim Tjernlund" <joakim.tjernlund@transmode.se>
Subject: Re: [v2 PATCH 1/2] powerpc32: adds handling of _PAGE_RO
Date: Wed, 17 Dec 2014 20:14:28 -0600 [thread overview]
Message-ID: <1418868868.5581.121.camel@freescale.com> (raw)
In-Reply-To: <20141217091431.D3F761A5E0D@localhost.localdomain>
On Wed, 2014-12-17 at 10:14 +0100, Christophe Leroy wrote:
> Some powerpc like the 8xx don't have a RW bit in PTE bits but a RO (Read Only) bit.
> This patch implements the handling of a _PAGE_RO flag to be used in place of _PAGE_RW
>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
>
> ---
> v2 is a complete rework compared to v1
>
> arch/powerpc/include/asm/pgtable-ppc32.h | 11 ++++++-----
> arch/powerpc/include/asm/pgtable.h | 10 +++++++---
> arch/powerpc/include/asm/pte-common.h | 27 ++++++++++++++++++---------
> arch/powerpc/mm/gup.c | 2 ++
> arch/powerpc/mm/mem.c | 2 +-
> arch/powerpc/mm/pgtable_32.c | 24 ++++++++++++++++++++----
> 6 files changed, 54 insertions(+), 22 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/pgtable-ppc32.h b/arch/powerpc/include/asm/pgtable-ppc32.h
> index 543bb8e..64ed9e1 100644
> --- a/arch/powerpc/include/asm/pgtable-ppc32.h
> +++ b/arch/powerpc/include/asm/pgtable-ppc32.h
> @@ -125,7 +125,7 @@ extern int icache_44x_need_flush;
> #ifndef __ASSEMBLY__
>
> #define pte_clear(mm, addr, ptep) \
> - do { pte_update(ptep, ~_PAGE_HASHPTE, 0); } while (0)
> + do { pte_update(ptep, ~_PAGE_HASHPTE, _PAGE_RO); } while (0)
Is this really necessary? It's already clearing the valid bit.
Likewise in several other places that set or check for _PAGE_RO on pages
for which no access is permitted.
> @@ -287,8 +287,9 @@ static inline void huge_ptep_set_wrprotect(struct mm_struct *mm,
> static inline void __ptep_set_access_flags(pte_t *ptep, pte_t entry)
> {
> unsigned long bits = pte_val(entry) &
> - (_PAGE_DIRTY | _PAGE_ACCESSED | _PAGE_RW | _PAGE_EXEC);
> - pte_update(ptep, 0, bits);
> + (_PAGE_DIRTY | _PAGE_ACCESSED | _PAGE_RW | _PAGE_RO |
> + _PAGE_EXEC);
> + pte_update(ptep, _PAGE_RO, bits);
> }
You're unconditionally clearing _PAGE_RO, and apparently relying on the
undocumented behavior of pte_update() to clear "clr" before setting
"set".
Instead I'd write this as:
unsigned long set = pte_val(entry) &
(_PAGE_DIRTY | _PAGE_ACCESSED | _PAGE_RW | _PAGE_EXEC);
unsigned long clr = pte_val(entry) & _PAGE_RO;
pte_update(ptep, clr, set);
-Scott
next prev parent reply other threads:[~2014-12-18 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 9:14 [v2 PATCH 1/2] powerpc32: adds handling of _PAGE_RO Christophe Leroy
2014-12-18 2:14 ` Scott Wood [this message]
2014-12-18 7:11 ` leroy christophe
2014-12-18 11:23 ` Scott Wood
2014-12-22 10:25 ` leroy christophe
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=1418868868.5581.121.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox