2 Aug
2019
2 Aug
'19
10:08 a.m.
Hi Dave,
On Wed, Jul 31, 2019 at 09:43:46AM -0700, Dave Hansen wrote:
On 7/25/19 6:50 AM, Vincenzo Frascino wrote:
With the relaxed ABI proposed through this document, it is now possible to pass tagged pointers to the syscalls, when these pointers are in memory ranges obtained by an anonymous (MAP_ANONYMOUS) mmap().
I don't see a lot of description of why this restriction is necessary. What's the problem with supporting MAP_SHARED?
We could support MAP_SHARED | MAP_ANONYMOUS (and based on some internal discussions, this would be fine with the hardware memory tagging as well). What we don't want in the ABI is to support file mmap() for top-byte-ignore (or MTE). If you see a use-case, please let us know.
--
Catalin