From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Richard Earnshaw <rearnsha@arm.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v4 4/6] linux: Add compatibility definitions to sys/prctl.h for MTE
Date: Mon, 21 Dec 2020 19:11:30 +0530 [thread overview]
Message-ID: <1c8ddeb6-e417-dfc0-13c5-a0da455571bf@gotplt.org> (raw)
In-Reply-To: <87wnxbwa5c.fsf@oldenburg2.str.redhat.com>
On 12/21/20 7:09 PM, Florian Weimer wrote:
> * Siddhesh Poyarekar:
>
>> On 12/19/20 12:59 AM, Richard Earnshaw via Libc-alpha wrote:
>>> Older versions of the Linux kernel headers obviously lack support
>>> for
>>> memory tagging, but we still want to be able to build in support when
>>> using those (obviously it can't be enabled on such systems).
>>> The linux kernel extensions are made to the platform-independent
>>> header (linux/prctl.h), so this patch takes a similar approach.
>>> ---
>>> sysdeps/unix/sysv/linux/sys/prctl.h | 18 ++++++++++++++++++
>>> 1 file changed, 18 insertions(+)
>>
>> Please put the additions into an architecture-specific
>> sysdeps/unix/sysv/linux/aarch64/sys/prctl.h and include_next this file
>> from there.
>
> This does not work for an installed header. A separate bits/ header is
> needed for such cases (if it is indeed required not to make the
> definitions generic, which is probably not the case here—that is,
> this part of Richard's patch can be used as-is).
Uff, indeed I didn't notice that it was an installed header. This is OK
as is then.
Thanks,
Siddhesh
next prev parent reply other threads:[~2020-12-21 13:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 19:29 [PATCH v4 0/6] Memory tagging support Richard Earnshaw
2020-12-18 19:29 ` [PATCH v4 1/6] config: Allow memory tagging to be enabled when configuring glibc Richard Earnshaw
2020-12-21 12:40 ` Siddhesh Poyarekar
2020-12-18 19:29 ` [PATCH v4 2/6] elf: Add a tunable to control use of tagged memory Richard Earnshaw
2020-12-21 12:42 ` Siddhesh Poyarekar
2020-12-18 19:29 ` [PATCH v4 3/6] malloc: Basic support for memory tagging in the malloc() family Richard Earnshaw
2020-12-21 13:27 ` Siddhesh Poyarekar
2020-12-21 13:46 ` Florian Weimer
2020-12-21 14:31 ` Richard Earnshaw
2020-12-21 14:31 ` Szabolcs Nagy
2020-12-18 19:29 ` [PATCH v4 4/6] linux: Add compatibility definitions to sys/prctl.h for MTE Richard Earnshaw
2020-12-21 13:32 ` Siddhesh Poyarekar
2020-12-21 13:34 ` Richard Earnshaw
2020-12-21 13:38 ` Siddhesh Poyarekar
2020-12-21 13:39 ` Florian Weimer
2020-12-21 13:41 ` Siddhesh Poyarekar [this message]
2020-12-18 19:29 ` [PATCH v4 5/6] aarch64: Add sysv specific enabling code for memory tagging Richard Earnshaw
2020-12-21 12:27 ` Szabolcs Nagy
2020-12-21 13:36 ` Siddhesh Poyarekar
2020-12-18 19:29 ` [PATCH v4 6/6] aarch64: Add aarch64-specific files for memory tagging support Richard Earnshaw
2020-12-21 12:44 ` Szabolcs Nagy
2020-12-21 12:50 ` Richard Earnshaw
2020-12-18 20:18 ` [PATCH v4 0/6] Memory " H.J. Lu
2020-12-21 12:28 ` Siddhesh Poyarekar
2020-12-21 13:44 ` Siddhesh Poyarekar
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=1c8ddeb6-e417-dfc0-13c5-a0da455571bf@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=rearnsha@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).