From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) by sourceware.org (Postfix) with ESMTPS id 132203864877 for ; Thu, 11 Feb 2021 21:40:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 132203864877 Received: by mail-ot1-x32a.google.com with SMTP id l23so6568871otn.10 for ; Thu, 11 Feb 2021 13:40:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5kddfw0FcX4uPAVhgSKR/nJfIvHjc6qOWG4WHSFEAMU=; b=ZFo4HM57qdpXguw/lufu3KJVjSHVtfzWYlH+w55QPn33WeEJnVQLO0pQ1+ovh2f14r p4WYblQIAyBylK/kZn0fdP+9uPn95g+38IZJthz20ykABvyJNoBJH5ChK4t0oAPzL34M d2lnYEvrou8np6ucDm673/HHTkmT/Zz87OhWY0yJgGXjc+WOeYX+TDbtUd62hkyBzlu1 4hW8FCvYC12K7J022Cbh5WXLrUxMmMPBjoxmfdKmWRqJkW9n4OQ3GFKWB1YHgoD5KOlI fRo8vZCuwJaoQm7qqiBE0QEFB2WCD5CwngAfTnkwVuEYupJXzTLBZZ9rfK45ILytaotz s1HQ== X-Gm-Message-State: AOAM530V5x8cqsF4Y8EZswGIaZgkmApYusOMiwbAXvXgQphWrAgYoppl Abw4A31054Na6lPYhax6XsfYMx7rzGKbNKb2Eek6CapC0fk= X-Google-Smtp-Source: ABdhPJz4xi9I+aeDC7/CWxslO9tcu2s8rz1K25rJmxkpWz4XZIBV3icSvFLfYNgeiTWSSrHEzSj9t07w4MGST31lyAE= X-Received: by 2002:a9d:4786:: with SMTP id b6mr23472otf.269.1613079630429; Thu, 11 Feb 2021 13:40:30 -0800 (PST) MIME-Version: 1.0 References: <20210211173711.71736-1-hjl.tools@gmail.com> In-Reply-To: From: "H.J. Lu" Date: Thu, 11 Feb 2021 13:39:54 -0800 Message-ID: Subject: Re: [RFC] : An API for tagged address To: Joseph Myers Cc: GNU C Library Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3030.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2021 21:40:32 -0000 On Thu, Feb 11, 2021 at 12:28 PM Joseph Myers 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 > already have in glibc, what corresponding features are involved on other ARM MTE is built on top of TBI. My supports LAM and TBI. It can be used to: 1. Enable LAM/TBI. 2. Make mommove LAM/TBI compatible. 3. Enable LAM in HWASAN. > architectures?) and what the API is intended to be useful for. A new API > also needs additions to the manual and NEWS - again, explaining things at > the user level. > > The header naming suggests installed headers, but you don't appear to be > installing them. I will install them in the final version. The complete LAM patch set is on users/intel/lam/master branch at https://gitlab.com/x86-glibc/glibc/-/tree/users/intel/lam/master > I don't see anything architecture-specific about the build logic, so I'd > expect all libc.abilist files to have the new functions rather than just a > few. The final version will update all libc.abilist files. Thanks. -- H.J.