From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Cc: Joseph Myers <joseph@codesourcery.com>, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [RFC] <sys/tagged-address.h>: An API for tagged address
Date: Fri, 12 Feb 2021 10:43:28 +0100 [thread overview]
Message-ID: <877dndmxj3.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOqLW2pn2-TZ0_sXk40Wr9+NU8BP3JfCGM3X4rQAHbEisg@mail.gmail.com> (H. J. Lu via Libc-alpha's message of "Thu, 11 Feb 2021 13:39:54 -0800")
* H. J. Lu via Libc-alpha:
> On Thu, Feb 11, 2021 at 12:28 PM Joseph Myers <joseph@codesourcery.com> wrote:
>>
>> On Thu, 11 Feb 2021, H.J. Lu via Libc-alpha wrote:
>>
>> > An API for tagged address:
>>
>> Please write a longer commit message, discussing what "tagged address" is,
>> which architectures have such a thing (the API should try to cover
>> whatever is common between architectures as far as possible - is this
>> meant to relate to AArch64 MTE, how does it relate to the MTE code we
>
> This API is for Intel LAM:
>
> https://www.phoronix.com/scan.php?page=news_item&px=Intel-LAM-Glibc#:~:text=Intel%20Linear%20Address%20Masking%20(LAM,bit%20linear%20addresses%20for%20metadata.&text=With%20LAM%20enabled%2C%20the%20processor,linear%20address%20to%20access%20memory.
>
> and ARM TBI:
>
> https://en.wikichip.org/wiki/arm/tbi
Do the setters/getters change process or thread properties?
The interface assumes that the tag bits are uniform across pointer
types. I think that's not true, at least from a historical perspective.
People complained that our protection key interfaces are too slow to be
useful. Do we need to find a way to inline the tag/untag operations?
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2021-02-12 9:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 17:37 H.J. Lu
2021-02-11 20:28 ` Joseph Myers
2021-02-11 21:39 ` H.J. Lu
2021-02-12 9:43 ` Florian Weimer [this message]
2021-02-12 13:06 ` H.J. Lu
2021-02-17 18:43 ` H.J. Lu
2021-02-17 21:58 ` H.J. Lu
2021-02-18 13:24 ` Szabolcs Nagy
2021-02-18 13:28 ` Florian Weimer
2021-02-18 13:50 ` Szabolcs Nagy
2021-02-18 22:32 ` H.J. Lu
2021-02-22 8:27 ` Szabolcs Nagy
2021-02-22 13:57 ` H.J. Lu
2021-02-18 13:17 ` Szabolcs Nagy
2021-02-18 13:21 ` Florian Weimer
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=877dndmxj3.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).