From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dave@treblig.org>
Cc: qemu-devel@nongnu.org,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Hanna Reitz" <hreitz@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
devel@lists.libvirt.org, "Stefan Weil" <sw@weilnetz.de>,
qemu-block@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [PATCH 05/12] util: add API to fetch the current thread id
Date: Wed, 20 Aug 2025 11:47:06 +0100 [thread overview]
Message-ID: <aKWnqqSdt0CFctcZ@redhat.com> (raw)
In-Reply-To: <aKUKPsen9jOvi_O0@gallifrey>
On Tue, Aug 19, 2025 at 11:35:26PM +0000, Dr. David Alan Gilbert wrote:
> * Daniel P. Berrangé (berrange@redhat.com) wrote:
> > For logging it is useful to include the current thread id. On
> > POSIX there is no standard API for this, so try the Linux gettid()
> > syscall preferentially, otherwise fallback to casting the result
> > of thread_self() to an integer.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > include/qemu/thread.h | 1 +
> > util/qemu-thread-posix.c | 11 +++++++++++
> > util/qemu-thread-win32.c | 5 +++++
> > 3 files changed, 17 insertions(+)
> >
> > diff --git a/include/qemu/thread.h b/include/qemu/thread.h
> > index 3a286bb3ef..96eee82679 100644
> > --- a/include/qemu/thread.h
> > +++ b/include/qemu/thread.h
> > @@ -215,6 +215,7 @@ void *qemu_thread_join(QemuThread *thread);
> > void qemu_thread_get_self(QemuThread *thread);
> > bool qemu_thread_is_self(QemuThread *thread);
> > G_NORETURN void qemu_thread_exit(void *retval);
> > +uint64_t qemu_thread_get_id(void);
> >
> > struct Notifier;
> > /**
> > diff --git a/util/qemu-thread-posix.c b/util/qemu-thread-posix.c
> > index 121d7ed69b..f240a93632 100644
> > --- a/util/qemu-thread-posix.c
> > +++ b/util/qemu-thread-posix.c
> > @@ -532,3 +532,14 @@ void *qemu_thread_join(QemuThread *thread)
> > }
> > return ret;
> > }
> > +
> > +uint64_t qemu_thread_get_id(void)
> > +{
> > +#ifdef CONFIG_GETTID
> > + return (uint64_t)gettid();
> > +#elif defined(SYS_gettid)
> > + return (uint64_t)syscall(SYS_gettid);
> > +#else
> > + return (uint64_t)pthread_self();
>
> My reading of the manpage is that is not guaranteed to be castable.
> It also explicitly says it's not the same as gettid. Albeit probably is.
Yeah, technically pthread_t could be a struct. Guess it depends how much
we care about strict standards portability, vs portability to our tested
set of platforms (macOS, *BSD)[1]. We could hardcode to 0 as an alternative.
With regards,
Daniel
[1] admittedly i've not actually compile tested this yet on non-Linux,
aside from Windows which uses the non-pthreads code.
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-08-20 10:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 20:26 [PATCH 00/12] util: sync error_report & qemu_log output more closely Daniel P. Berrangé
2025-08-19 20:26 ` [PATCH 01/12] include: define constant for early constructor priority Daniel P. Berrangé
2025-08-19 20:26 ` [PATCH 02/12] monitor: initialize global data from a constructor Daniel P. Berrangé
2025-08-19 20:26 ` [PATCH 03/12] system: unconditionally enable thread naming Daniel P. Berrangé
2025-08-19 22:00 ` Dr. David Alan Gilbert
2025-08-19 20:27 ` [PATCH 04/12] util: set the name for the 'main' thread Daniel P. Berrangé
2025-08-19 23:18 ` Dr. David Alan Gilbert
2025-08-20 10:29 ` Daniel P. Berrangé
2025-08-19 20:27 ` [PATCH 05/12] util: add API to fetch the current thread id Daniel P. Berrangé
2025-08-19 21:38 ` Richard Henderson
2025-08-19 23:35 ` Dr. David Alan Gilbert
2025-08-20 10:47 ` Daniel P. Berrangé [this message]
2025-08-19 20:27 ` [PATCH 06/12] util: add API to fetch the current thread name Daniel P. Berrangé
2025-08-19 21:50 ` Richard Henderson
2025-08-20 10:50 ` Daniel P. Berrangé
2025-08-19 20:27 ` [PATCH 07/12] util: introduce common helper for error-report & log code Daniel P. Berrangé
2025-08-19 21:57 ` Richard Henderson
2025-08-20 11:00 ` Daniel P. Berrangé
2025-08-19 20:27 ` [PATCH 08/12] util: convert error-report & log to message API for timestamp Daniel P. Berrangé
2025-08-19 22:02 ` Richard Henderson
2025-08-20 11:12 ` Daniel P. Berrangé
2025-08-29 18:07 ` Daniel P. Berrangé
2025-08-19 20:27 ` [PATCH 09/12] util: add support for formatting a workload name in messages Daniel P. Berrangé
2025-08-19 20:27 ` [PATCH 10/12] util: add support for formatting a program " Daniel P. Berrangé
2025-08-19 20:27 ` [PATCH 11/12] util: add support for formatting thread info " Daniel P. Berrangé
2025-08-19 20:27 ` [PATCH 12/12] util: add brackets around guest name in message context Daniel P. Berrangé
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=aKWnqqSdt0CFctcZ@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dave@treblig.org \
--cc=devel@lists.libvirt.org \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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 NNTP newsgroup(s).