From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, keescook@chromium.org,
dave.martin@arm.com, catalin.marinas@arm.com
Subject: Re: [PATCH v3 0/2] arm64: Support Enhanced PAN
Date: Fri, 12 Mar 2021 11:18:36 +0000 [thread overview]
Message-ID: <3ce499a0-b427-b465-c5e9-5dda2594107a@arm.com> (raw)
In-Reply-To: <20210126110928.GC29467@willie-the-truck>
On 1/26/21 11:09 AM, Will Deacon wrote:
> On Tue, Jan 19, 2021 at 04:07:21PM +0000, Vladimir Murzin wrote:
>> ARM architecture gains support of Enhanced Privileged Access Never
>> (EPAN) which allows Privileged Access Never to be used with
>> Execute-only mappings.
>>
>> As a consequence 24cecc377463 ("arm64: Revert support for execute-only
>> user mappings") can be revisited and re-enabled.
>
> Does ptdump.c need updating too?
I had a look at ptdump.c and IIUIC that supposed to pretty print bits for
page table entry. Thus with EPAN supported we stop seeing "USR" for execute
only mapping, but it correctly reflects state of pte. What I'm missing?
Cheers
Vladimir
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-03-12 11:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 16:07 [PATCH v3 0/2] arm64: Support Enhanced PAN Vladimir Murzin
2021-01-19 16:07 ` [PATCH v3 1/2] arm64: Support execute-only permissions with " Vladimir Murzin
2021-01-26 11:03 ` Will Deacon
2021-01-26 12:05 ` Catalin Marinas
2021-01-26 12:23 ` Will Deacon
2021-03-12 11:19 ` Vladimir Murzin
2021-03-12 11:20 ` Will Deacon
2021-03-12 12:23 ` Catalin Marinas
2021-03-12 11:17 ` Vladimir Murzin
2021-01-19 16:07 ` [PATCH v3 2/2] arm64: Introduce HWCAPS2_EXECONLY Vladimir Murzin
2021-01-26 11:07 ` Will Deacon
2021-01-26 11:09 ` [PATCH v3 0/2] arm64: Support Enhanced PAN Will Deacon
2021-03-12 11:18 ` Vladimir Murzin [this message]
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=3ce499a0-b427-b465-c5e9-5dda2594107a@arm.com \
--to=vladimir.murzin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dave.martin@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.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).