From: Khem Raj <raj.khem@gmail.com>
To: musl@lists.openwall.com, Michael Forney <mforney@mforney.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [musl] Support SIGEV_THREAD_ID
Date: Sat, 31 Oct 2020 22:46:23 -0700 [thread overview]
Message-ID: <e78e55c5-07fd-4812-20b3-cf2306f1d114@gmail.com> (raw)
In-Reply-To: <CAGw6cBvDJm+9tJg8dNeyH0bXEXQ_NpCN5+87_9ZRRiZ9=jF18g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
On 10/30/20 2:22 PM, Michael Forney wrote:
> On 2019-08-01, Florian Weimer <fweimer@redhat.com> wrote:
>> * James Y. Knight:
>>
>>> There seems to be some debate in glibc over whether this API should be
>>> supported, due to the long-standing debate about "pthread_t" vs
>>> "kernel tid" APIs. (And this API uses kernel tids, of course.)
>>
>> The debate is over and has been decided in favor of supporting TIDs. We
>> just have a backlog of interfaces for which we need to add support.
>
> Hi Florian,
>
> Am I interpreting you correctly that glibc intends to add a
> sigev_notify_thread_id define to access this field in struct sigevent?
> I plan to send a patch to qemu to use sigev_notify_thread_id over
> _sigev_un.tid if it is available, and I just want to confirm that
> glibc intends to follow suit before I mention that in the commit
> message.
we will need something similar for gperftools as well.
>
> Thanks
>
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2373 bytes --]
next prev parent reply other threads:[~2020-11-01 5:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 16:15 James Y Knight
2019-08-01 16:24 ` Florian Weimer
2019-08-01 16:45 ` Rich Felker
2020-10-30 21:22 ` [musl] " Michael Forney
2020-11-01 5:46 ` Khem Raj [this message]
2020-11-02 12:55 ` Florian Weimer
2019-08-01 16:49 ` Rich Felker
2019-08-01 18:00 ` James Y Knight
2019-08-06 2:06 ` Rich Felker
2020-08-18 0:32 ` [musl] " Rich Felker
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=e78e55c5-07fd-4812-20b3-cf2306f1d114@gmail.com \
--to=raj.khem@gmail.com \
--cc=fweimer@redhat.com \
--cc=mforney@mforney.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).