linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: steve.capper@linaro.org (Steve Capper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/2] PTE fixes for ARM LPAE
Date: Fri, 28 Mar 2014 14:22:32 +0000	[thread overview]
Message-ID: <1396016554-5843-1-git-send-email-steve.capper@linaro.org> (raw)

This series fixes a couple of problems that I have come across on ARM
with LPAE.
 1) Some pte accessors can have their results cancelled out by a
    downcast. This is addressed by the first patch.

 2) It is impossible to distinguish between clean writable ptes and
    read only ptes. This is addressed by the second patch.

The big change in V3 is going back to the pte_isset macros, also an
additional macro, pte_isclear, is introduced. For cases where the bits
to be tested are in the lower 32-bits of the pte, the double logical
invert is dropped.

Steve Capper (2):
  arm: mm: Introduce pte_isset and pte_isclear
  arm: mm: Switch back to L_PTE_WRITE

 arch/arm/include/asm/pgtable-2level.h |  2 +-
 arch/arm/include/asm/pgtable-3level.h |  1 +
 arch/arm/include/asm/pgtable.h        | 50 +++++++++++++++++++----------------
 arch/arm/mm/dump.c                    |  8 +++---
 arch/arm/mm/mmu.c                     | 25 +++++++++---------
 arch/arm/mm/proc-macros.S             | 16 +++++------
 arch/arm/mm/proc-v7-2level.S          |  6 ++---
 arch/arm/mm/proc-v7-3level.S          |  4 ++-
 arch/arm/mm/proc-xscale.S             |  4 +--
 9 files changed, 62 insertions(+), 54 deletions(-)

-- 
1.8.1.4

             reply	other threads:[~2014-03-28 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 14:22 Steve Capper [this message]
2014-03-28 14:22 ` [PATCH V3 1/2] arm: mm: Introduce pte_isset and pte_isclear Steve Capper
2014-03-28 14:22 ` [PATCH V3 2/2] arm: mm: Switch back to L_PTE_WRITE Steve Capper
2014-05-01 12:46 ` [PATCH V3 0/2] PTE fixes for ARM LPAE Steve Capper

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=1396016554-5843-1-git-send-email-steve.capper@linaro.org \
    --to=steve.capper@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).