From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1AE67D29FEF for ; Wed, 14 Jan 2026 11:29:09 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1vfz3k-0001LP-5k; Wed, 14 Jan 2026 06:29:08 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1vfz3i-0001GA-Id for qemu-rust@nongnu.org; Wed, 14 Jan 2026 06:29:07 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1vfz3f-0001wo-Kd for qemu-rust@nongnu.org; Wed, 14 Jan 2026 06:29:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1768390143; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=D4Di8ekOKy9gTaxd4biHPnTvnjOFZXBL2ZQYBNaA0vs=; b=RWrB324ESAulEwMUNGfy2Rb63z7NrheS3V2aT7nV1ItOmZlAVBB9RS4erZfpdqTajaADex OFN7pfuwSCP532Dk0DqfgeXfM/2VGy8h0OjvOIcX0gfKgttbrvS4mVnyyV2LAtj+GmaE9M znKNrMsIWS7aGF8BhXeKU6H1P8s09fI= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-610-TmcOmbQyODegkaU4lntNIA-1; Wed, 14 Jan 2026 06:28:59 -0500 X-MC-Unique: TmcOmbQyODegkaU4lntNIA-1 X-Mimecast-MFC-AGG-ID: TmcOmbQyODegkaU4lntNIA_1768390138 Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id E31421955F34; Wed, 14 Jan 2026 11:28:57 +0000 (UTC) Received: from redhat.com (unknown [10.42.28.41]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id E0DB019560A2; Wed, 14 Jan 2026 11:28:48 +0000 (UTC) Date: Wed, 14 Jan 2026 11:28:43 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Paolo Bonzini Cc: Markus Armbruster , qemu-devel@nongnu.org, Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= , Manos Pitsidianakis , Hanna Reitz , Gerd Hoffmann , Christian Schoenebeck , "Dr. David Alan Gilbert" , =?utf-8?Q?Marc-Andr=C3=A9?= Lureau , devel@lists.libvirt.org, qemu-block@nongnu.org, qemu-rust@nongnu.org, Stefan Weil , Kevin Wolf , Richard Henderson Subject: Re: [PATCH v5 08/24] util: add API to fetch the current thread name Message-ID: References: <20260108170338.2693853-1-berrange@redhat.com> <20260108170338.2693853-9-berrange@redhat.com> <878qe1c17b.fsf@pond.sub.org> <874iopacr0.fsf@pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.2.14 (2025-02-20) X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 Received-SPF: pass client-ip=170.10.133.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-rust@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: QEMU Rust-related patches and discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Errors-To: qemu-rust-bounces+qemu-rust=archiver.kernel.org@nongnu.org Sender: qemu-rust-bounces+qemu-rust=archiver.kernel.org@nongnu.org On Tue, Jan 13, 2026 at 04:49:53PM +0100, Paolo Bonzini wrote: > On Tue, Jan 13, 2026 at 2:00 PM Markus Armbruster wrote: > > > > Tempted to store the thread name in TLS and call it a day. > > > > > > Using the official APIs in this way ensures that the thread name is > > > visible outside QEMU. For example when debugging in GDB, which IMHO > > > is an important benefit. > > > > I didn't mean to suggest not to set the "official" thread name. > > > > This patch retrieves the "official" thread name back. Takes a bit of > > system-specific code, including Meson magic. We could instead hold on > > to our own copy, and just use that. > > Yes, I think that's what we're going to do anyway due to my remark on > patch 7/24. That doesn't alter things. The constructor merely initialzies the name for the main thread. We'll still use pthread APIs for all other threads. With regards, Daniel -- |: 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 :|