unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	Szabolcs Nagy <szabolcs.nagy@arm.com>,
	Joseph Myers <joseph@codesourcery.com>,
	"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH v5 1/1] <sys/tagged-address.h>: An API for tagged address
Date: Fri, 20 Aug 2021 09:30:00 -0700	[thread overview]
Message-ID: <CAMe9rOrkSTr=iavOJfSiW5LYWswQT1qBgvyuRnJzuFy8ETctfg@mail.gmail.com> (raw)
In-Reply-To: <87r1eoulq6.fsf@oldenburg.str.redhat.com>

On Fri, Aug 20, 2021 at 9:25 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * H. J. Lu:
>
> > On Thu, Aug 12, 2021 at 5:01 AM Szabolcs Nagy <szabolcs.nagy@arm.com> wrote:
> >>
> >> The 08/12/2021 10:36, Florian Weimer wrote:
> >> > * H. J. Lu:
> >> > > +@deftypefun int set_tagged_address_mask (uintptr_t @var{mask})
> >> > > +@standards{GNU, sys/tagged-address.h}
> >> > > +@safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
> >> > > +Set the mask for address bits used in address translation to @var{mask}.
> >> > > +Only bits set in @var{mask} will be used in address translation.  The
> >> > > +return value is @code{0} on success and @code{-1} on failure.  This
> >> > > +function can be called only once before @code{main}.
> >> >
> >> > Again the restriction around @code{main} is unclear.  If it's “before
> >> > allocating memory” or “before starting threads”, than we should say
> >> > that.
> >>
> >> it should be at least before thread creation on aarch64.
> >
> > Before main is before thread creation and before main is safer
> > than before thread creation.
>
> You can create threads from ELF constructors, and those run before main.
> (Although this tends to run into deadlocks in our implementation.)

I will change the wording to before man AND thread creation.

-- 
H.J.

  reply	other threads:[~2021-08-20 16:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 13:13 [PATCH v5 0/1] RFC: Add <sys/tagged-address.h> H.J. Lu via Libc-alpha
2021-08-05 13:13 ` [PATCH v5 1/1] <sys/tagged-address.h>: An API for tagged address H.J. Lu via Libc-alpha
2021-08-05 17:26   ` Joseph Myers
2021-08-05 17:41     ` H.J. Lu via Libc-alpha
2021-08-05 17:54       ` Joseph Myers
2021-08-05 19:33         ` H.J. Lu via Libc-alpha
2021-08-12  8:36   ` Florian Weimer via Libc-alpha
2021-08-12 12:01     ` Szabolcs Nagy via Libc-alpha
2021-08-17 12:32       ` Szabolcs Nagy via Libc-alpha
2021-08-17 12:53         ` H.J. Lu via Libc-alpha
2021-08-17 14:59           ` Szabolcs Nagy via Libc-alpha
2021-08-17 15:37             ` H.J. Lu via Libc-alpha
2021-08-20 16:14       ` H.J. Lu via Libc-alpha
2021-08-20 16:25         ` Florian Weimer via Libc-alpha
2021-08-20 16:30           ` H.J. Lu via Libc-alpha [this message]
2021-08-20 23:26     ` H.J. Lu via Libc-alpha
2021-08-21 16:10       ` Sunil Pandey via Libc-alpha
2021-08-21 16:37         ` H.J. Lu via Libc-alpha
2021-08-21 21:20           ` Sunil Pandey via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMe9rOrkSTr=iavOJfSiW5LYWswQT1qBgvyuRnJzuFy8ETctfg@mail.gmail.com' \
    --to=libc-alpha@sourceware.org \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=joseph@codesourcery.com \
    --cc=kirill.shutemov@linux.intel.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).