On Wed, 25 Feb 2026 at 16:30, Daniel P. Berrangé <[email protected]> wrote: > > On Thu, Feb 19, 2026 at 10:29:56AM +0000, Peter Maydell wrote: > > On Wed, 11 Feb 2026 at 15:29, Daniel P. Berrangé <[email protected]> > > wrote: > > > After: > > > > > > # qemu-system-x86_64 -object tls-creds-x509,id=t0,dir=fish -d > > > 'trace:qcrypto*' > > > qemu-system-x86_64: (772366:main): qcrypto_tls_creds_x509_load TLS > > > creds x509 load creds=0x560db818e080 dir=fish > > > qemu-system-x86_64: (772366:main): qcrypto_tls_creds_get_path TLS creds > > > path creds=0x560db818e080 filename=ca-cert.pem path=<none> > > > qemu-system-x86_64: (772366:main): Unable to access credentials > > > fish/ca-cert.pem: No such file or directory > > > > Even more output enabled by default that is pretty useless for most > > uses of tracepoints and debug logging :-( > > Getting the thread info in qemu log output was the original primary > motivating factor in this series. This short example doesn't show > it, but when debugging/tracing QEMU it is pretty important to > understand which messages are coming from different threads, so we > can correctly interpret the control flow. Pretty much every logging > framework these days will include some thread identifier by default, > and IMHO it is reasonable to do this by default in QEMU too.
I have basically never found that I wanted to know in QEMU tracing which thread was involved, so I would dispute its importance in the general case. There's plenty of other things that would be more interesting to me to log by default: for instance in pretty much all our tracepoints in devices we don't have any indication of which device of possibly several instantiated in the system is the one producing this log output; having an easy way to have the tracepoints include e.g. the QOM path of the device involved would be nice. I don't object to providing optional logging of the host thread for people and cases where it's useful. But it's pretty useless to me, and if we always enable by default all the optional stuff that might be useful to somebody then the trace lines end up being a mile long and trace log files can become huge. Why can't we have this be something like -d thread-ids,trace:qcrypto* so people who want it can turn it on and people who don't want it don't get it? thanks -- PMM
