From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Joseph Myers <joseph@codesourcery.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Sunil K Pandey <skpgkp2@gmail.com>
Subject: Re: [PATCH v7 0/1] RFC: Add <sys/tagged-address.h>
Date: Mon, 15 Nov 2021 05:49:14 -0800 [thread overview]
Message-ID: <CAMe9rOoja-J1-2JKzLu_S2PXZKGyitg4M996DAh1zt=tj5V3Rg@mail.gmail.com> (raw)
In-Reply-To: <87mtm5h7a5.fsf@oldenburg.str.redhat.com>
On Mon, Nov 15, 2021 at 5:34 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * H. J. Lu:
>
> > By default, the number of the address bits used in address translation
> > is the number of address bits. But it can be changed by ARM Top-byte
> > Ignore (TBI) or Intel Linear Address Masking (LAM).
> >
> > <sys/tagged-address.h> provides an API for tagged address manipulation.
>
> H.J.,
>
> we had an off-list discussion regarding this, and I want to double-check
> if my recollection of the conclusion is correct.
>
> Basically, we said that we would try to enable HWSAN on x86-64 as well
> (using Intel LAM) *without* glibc changes or a new ABI. Once we have a
> better understanding of how address tagging is used/could be used by
> applications, we plan to define a general-purpose programming interface
> for it.
I withdrew this patch.
My current LAM patch is
https://gitlab.com/x86-glibc/glibc/-/commit/9d8fb211169fe677d3feca74aef5e87595f934ef
I will submit it after the LAM kernel interface is finalized.
--
H.J.
prev parent reply other threads:[~2021-11-15 13:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 16:53 H.J. Lu
2021-09-24 16:53 ` [PATCH v7 1/1] <sys/tagged-address.h>: An API for tagged address H.J. Lu
2021-10-04 13:58 ` H.J. Lu
2021-09-24 18:08 ` [PATCH v7 0/1] RFC: Add <sys/tagged-address.h> Joseph Myers
2021-09-24 18:39 ` H.J. Lu
2021-09-24 18:53 ` Joseph Myers
2021-09-24 18:58 ` H.J. Lu
2021-09-24 19:34 ` Joseph Myers
2021-09-24 22:00 ` H.J. Lu
2021-11-15 13:34 ` Florian Weimer
2021-11-15 13:49 ` H.J. Lu [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='CAMe9rOoja-J1-2JKzLu_S2PXZKGyitg4M996DAh1zt=tj5V3Rg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=libc-alpha@sourceware.org \
--cc=skpgkp2@gmail.com \
--cc=szabolcs.nagy@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 read-only IMAP folder(s) and NNTP newsgroup(s).