From: "Ross Burton" <ross@burtonini.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] glibc: Enable memory tagging for aarch64
Date: Mon, 24 May 2021 11:14:46 +0100 [thread overview]
Message-ID: <CAAnfSTuiyaysU6ws05KEZ2W=5sEanWNa+kLFUFjj6k=X6Dg1Cg@mail.gmail.com> (raw)
In-Reply-To: <20210523144532.325221-1-raj.khem@gmail.com>
+1 from me, I had the same patch locally that I was about to send :)
I do wonder if we should start using that PACKAGECONFIG for these
tunables, as on non-MTE hardware there is an overhead (albeit small).
Ross
On Sun, 23 May 2021 at 15:45, Khem Raj <raj.khem@gmail.com> wrote:
>
> Glibc on aarch64 has a memory tagging option that can be enabled
> via GLIBC_TUNABLES="glibc.mem.tagging=$SOMETHING" when glibc
> is built with memory tagging support and the kernel/HW supports
> MTE. There should be no side effects unless the user turns it
> on with approprate HW support
>
> Linux 5.4 headers and binutils 2.33.1 or newer is needed.
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> v2: Rebased
>
> meta/recipes-core/glibc/glibc_2.33.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/glibc/glibc_2.33.bb b/meta/recipes-core/glibc/glibc_2.33.bb
> index 75a1f36d6b..c805755bb9 100644
> --- a/meta/recipes-core/glibc/glibc_2.33.bb
> +++ b/meta/recipes-core/glibc/glibc_2.33.bb
> @@ -95,6 +95,7 @@ EXTRA_OECONF += "${@get_libc_fpu_setting(bb, d)}"
>
> EXTRA_OECONF_append_x86 = " --enable-cet"
> EXTRA_OECONF_append_x86-64 = " --enable-cet"
> +EXTRA_OECONF_append_aarch64 = " --enable-memory-tagging"
>
> PACKAGECONFIG ??= "nscd"
> PACKAGECONFIG[nscd] = "--enable-nscd,--disable-nscd"
> --
> 2.31.1
>
>
>
>
next prev parent reply other threads:[~2021-05-24 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 14:45 [PATCH v2] glibc: Enable memory tagging for aarch64 Khem Raj
2021-05-24 10:14 ` Ross Burton [this message]
2021-05-24 14:34 ` [OE-core] " Khem Raj
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='CAAnfSTuiyaysU6ws05KEZ2W=5sEanWNa+kLFUFjj6k=X6Dg1Cg@mail.gmail.com' \
--to=ross@burtonini.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.