From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,
	RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 25782 invoked from network); 30 Oct 2020 21:22:26 -0000
Received: from mother.openwall.net (195.42.179.200)
  by inbox.vuxu.org with ESMTPUTF8; 30 Oct 2020 21:22:26 -0000
Received: (qmail 5653 invoked by uid 550); 30 Oct 2020 21:22:23 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 5635 invoked from network); 30 Oct 2020 21:22:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=mforney-org.20150623.gappssmtp.com; s=20150623;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=IwM+vZRvYhwurm7NGjnkhXCSzvgikz2VBHYKoNhunmU=;
        b=vd6v+tSKJNaxVid4mBvzKh3F5Qh79MGsM1IfhHLPMQith3OlAoZfVtVZcQXKuivB65
         OrGUtJxzXojd93JLoIPlRrw3db0CYg9cqlxK3a7Oa5nCsMAgGmm2r3qVrLExHXXlZ71P
         4lyCALuDUqT49D2/kc/53tHuTR4cgJ9BYVQM6/CyPJTLnIhkJNvLfbJr0ma7IOGBgBA6
         4ukUDNC5p15OJYQx6jyfgLXELXMouRRNsgR+ydmG7jnkUFFHN3n/lzvpIzIdyWJQkbI1
         i6e+zspF5rOc/lVieblu3BhIRHnGwC+rIihseKK2WK8bf4LF+pxo9JIVWWgjj9C+hENO
         ePWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=IwM+vZRvYhwurm7NGjnkhXCSzvgikz2VBHYKoNhunmU=;
        b=qKnyzPsVsN3fV2amNkObfDT0Sqeg1KPg6NVpkDsJ9+2xNvqSkYYsoIZ8cx1sRmgiHc
         wh/qDiwoiUg3KhoNZuwX+lWCJKgWNwPOJK4EIbc5hPJP5NI/axbSxPY/78QzAj9dceY5
         77OzvCE6Uw+Mg2qWam0Dchrr+MvZMsF+I1i8Z0lt9WtcPOd+iAEybOmlyyM0EJzzo5m2
         zcYHdWfq254Fu9p8LGPQpYcfuABxr0bAp7czbtkjlcrYHK6wnwwqtKl9F4b96sW2MqBa
         Qcihuhp+fGzNbrFBTylobd2GR2XkUU//SVKg7PoJvIzMqw79XZ4EQ8v9yHdEq2mZB9yk
         513Q==
X-Gm-Message-State: AOAM532LUsMowyZBFDwi9z9mJ04PcTTijl3gCnYRY48uf9XycXD3Ca6u
	TLLllc5xvBBVCcQW1t+/wWunKcSxh/i8+NOBWvxXAA==
X-Google-Smtp-Source: ABdhPJwTSjVaEmblCqcgoOUQUkc2xUJru5bTJaJLSlpusBFM9JM0gRKHp+pni1PqGtFNYWZHigR601ExBriWiBHOzl4=
X-Received: by 2002:a92:6703:: with SMTP id b3mr3274770ilc.125.1604092930319;
 Fri, 30 Oct 2020 14:22:10 -0700 (PDT)
MIME-Version: 1.0
X-Originating-IP: [73.70.188.119]
In-Reply-To: <87h870hn0g.fsf@oldenburg2.str.redhat.com>
References: <CAA2zVHoRQzQM6zc4Qvc7abwB4=EWotrN5ntoN6nw986OkGEFKw@mail.gmail.com>
 <87h870hn0g.fsf@oldenburg2.str.redhat.com>
From: Michael Forney <mforney@mforney.org>
Date: Fri, 30 Oct 2020 14:22:09 -0700
Message-ID: <CAGw6cBvDJm+9tJg8dNeyH0bXEXQ_NpCN5+87_9ZRRiZ9=jF18g@mail.gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: musl@lists.openwall.com
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [musl] Support SIGEV_THREAD_ID

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.

Thanks