From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [Question] A question about arm64 pte
Date: Mon, 16 Jan 2017 11:56:07 +0000 [thread overview]
Message-ID: <20170116115606.GA6832@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <d284f510-f025-db84-f21e-a5b167d4bcd2@huawei.com>
On Mon, Jan 16, 2017 at 06:08:47PM +0800, Yisheng Xie wrote:
> I have question about arm64 pte.
I assume the context is ARMv8.0 (without hardware DBM support).
> For arm64, PTE_WRITE?== PTE_DBM? is to mark whether the page is writable,
> and PTE_DIRTY is to mark whether the page is dirty.
> However, PTE_RDONLY is only cleared when both PTE_WRITE and PTE_DIRTY are set.
That's what set_pte_at() does.
> Is that means that the page is still writable when PTE_RDONLY is set with PTE_WRITE?
No. On ARMv8.0, PTE_WRITE is a software only bit while PTE_RDONLY
describes the actual hardware permission. If set_pte_at() does not clear
the PTE_RDONLY bit (PTE_DIRTY not set), the page is read-only even
though PTE_WRITE may be set.
> But in ARM Architecture Reference Manual for ARMv8,
> when PTE_RDONLY is set(AP[2:1] = 0b1x), Acess from EL1 is Ready only?
Yes.
> so what is the really means of the PTE_RDONLY?
Read-only. On ARMv8.0, PTE_WRITE is irrelevant from a hardware
perspective.
--
Catalin
next prev parent reply other threads:[~2017-01-16 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 10:08 [Question] A question about arm64 pte Yisheng Xie
2017-01-16 11:56 ` Catalin Marinas [this message]
2017-01-16 12:39 ` Yisheng Xie
2017-01-16 12:57 ` Steve Capper
2017-01-17 1:04 ` Yisheng Xie
2017-01-16 14:36 ` Catalin Marinas
2017-01-16 14:39 ` Catalin Marinas
2017-01-17 1:02 ` Yisheng Xie
2017-01-17 3:53 ` Yisheng Xie
2017-01-17 11:45 ` Catalin Marinas
2017-01-17 12:02 ` Yisheng Xie
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=20170116115606.GA6832@e104818-lin.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).