From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-arch@vger.kernel.org, linux-doc@vger.kernel.org,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Andrey Konovalov <andreyknvl@google.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Will Deacon <will.deacon@arm.com>,
Dave Hansen <dave.hansen@intel.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>
Subject: [PATCH v7 0/2] arm64 tagged address ABI
Date: Wed, 7 Aug 2019 16:53:19 +0100 [thread overview]
Message-ID: <20190807155321.9648-1-catalin.marinas@arm.com> (raw)
Hi,
Thanks for the feedback so far. This is an updated series documenting
the AArch64 Tagged Address ABI as implemented by these patches:
http://lkml.kernel.org/r/cover.1563904656.git.andreyknvl@google.com
Version 6 of the documentation series is available here:
http://lkml.kernel.org/r/20190725135044.24381-1-vincenzo.frascino@arm.com
Changes in v7:
- Dropped the MAP_PRIVATE requirements for tagged pointers for both
anonymous and file mappings. One reason is that we can't enforce such
restriction anyway. The other reason is that a future series
implementing support for the hardware MTE will detect
incompatibilities of the new PROT_MTE flag with various mmap()
options.
- As a consequence of the above, I removed Szabolcs ack as I'm not sure
he's ok with the change.
- Clarified the sysctl and prctl() interaction and reordered the
descriptions.
- Reworded the prctl(PR_SET_MM) restrictions.
- Removed the description of the tag preservation from the first patch
as it didn't really make sense (the syscall ABI has always preserved
all registers other than x0 on return to user).
- s/ARM64/AArch64/ for consistency with the tagged-pointers.rst
document.
- Other minor rewordings.
Vincenzo Frascino (2):
arm64: Define Documentation/arm64/tagged-address-abi.rst
arm64: Relax Documentation/arm64/tagged-pointers.rst
Documentation/arm64/tagged-address-abi.rst | 151 +++++++++++++++++++++
Documentation/arm64/tagged-pointers.rst | 23 +++-
2 files changed, 167 insertions(+), 7 deletions(-)
create mode 100644 Documentation/arm64/tagged-address-abi.rst
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-08-07 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 15:53 Catalin Marinas [this message]
2019-08-07 15:53 ` [PATCH v7 1/2] arm64: Define Documentation/arm64/tagged-address-abi.rst Catalin Marinas
2019-08-07 20:38 ` Dave Hansen
2019-08-08 9:25 ` Szabolcs Nagy
2019-08-08 16:20 ` Szabolcs Nagy
2019-08-08 16:27 ` Dave Martin
2019-08-08 17:27 ` Catalin Marinas
2019-08-09 14:10 ` Dave Hansen
2019-08-12 17:36 ` Catalin Marinas
2019-08-13 11:10 ` Dave Martin
2019-08-08 16:30 ` Szabolcs Nagy
2019-08-08 17:04 ` Will Deacon
2019-08-12 10:46 ` Andrew Murray
2019-08-12 17:17 ` Catalin Marinas
2019-08-07 15:53 ` [PATCH v7 2/2] arm64: Relax Documentation/arm64/tagged-pointers.rst Catalin Marinas
2019-08-08 17:06 ` Will Deacon
2019-08-08 9:32 ` [PATCH v7 0/2] arm64 tagged address ABI Szabolcs Nagy
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=20190807155321.9648-1-catalin.marinas@arm.com \
--to=catalin.marinas@arm.com \
--cc=andreyknvl@google.com \
--cc=dave.hansen@intel.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=szabolcs.nagy@arm.com \
--cc=vincenzo.frascino@arm.com \
--cc=will.deacon@arm.com \
/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).