From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Preserve L_PTE_VALID in pte_modify()
Date: Mon, 25 Feb 2013 14:51:10 +0000 [thread overview]
Message-ID: <20130225145110.GA7838@localhost.cambridge.arm.com> (raw)
In-Reply-To: <20130225144355.GD25276@mudshark.cambridge.arm.com>
On Mon, Feb 25, 2013 at 02:43:56PM +0000, Will Deacon wrote:
> Hi Catalin,
>
> On Mon, Feb 18, 2013 at 04:21:50PM +0000, Will Deacon wrote:
> > On Tue, Feb 12, 2013 at 06:25:50PM +0000, Catalin Marinas wrote:
> > > Following commit 26ffd0d4 (ARM: mm: introduce present, faulting entries
> > > for PAGE_NONE), if a page has been mapped as PROT_NONE, the L_PTE_VALID
> > > bit is cleared by the set_pte_ext() code. With LPAE the software and
> > > hardware pte share the same location and subsequent modifications of pte
> > > range (change_protection()) will leave the L_PTE_VALID bit cleared.
> > >
> > > This patch adds the L_PTE_VALID bit to the newprot mask in pte_modify().
> > >
> > > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> > > Reported-by: Subash Patel <subash.rp@samsung.com>
> > > Tested-by: Subash Patel <subash.rp@samsung.com>
> > > Cc: Will Deacon <will.deacon@arm.com>
> >
> > This matches what I did for arm64, so:
> >
> > Acked-by: Will Deacon <will.deacon@arm.com>
>
> Can you put this into the patch system please?
Already picked by rmk (I don't remember the patch number).
--
Catalin
next prev parent reply other threads:[~2013-02-25 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 18:25 [PATCH] arm: Preserve L_PTE_VALID in pte_modify() Catalin Marinas
2013-02-18 16:21 ` Will Deacon
2013-02-25 14:43 ` Will Deacon
2013-02-25 14:51 ` Catalin Marinas [this message]
2013-02-25 14:54 ` Will Deacon
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=20130225145110.GA7838@localhost.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--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).