From: Peter Xu <peterx@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Fam Zheng" <famz@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] qemu-thread: always keep the posix wrapper layer
Date: Wed, 11 Apr 2018 11:18:26 +0800 [thread overview]
Message-ID: <20180411031826.GA13887@xz-mi> (raw)
In-Reply-To: <63211daf-4cda-163c-cb45-6fa3ac7e3cc5@redhat.com>
On Tue, Apr 10, 2018 at 08:35:40AM -0500, Eric Blake wrote:
> On 04/10/2018 07:49 AM, Peter Xu wrote:
> > We will conditionally have a wrapper layer depending on whether the host
> > has the PTHREAD_SETNAME capability. It complicates stuff. Let's just
> > keep the wrapper there, meanwhile we opt out the pthread_setname_np()
> > call only. The layer can be helpful in future patches to pass data from
> > the parent thread to the child thread.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > util/qemu-thread-posix.c | 33 +++++++++++++--------------------
> > 1 file changed, 13 insertions(+), 20 deletions(-)
> >
> > diff --git a/util/qemu-thread-posix.c b/util/qemu-thread-posix.c
> > index b789cf32e9..3ae96210d6 100644
> > --- a/util/qemu-thread-posix.c
> > +++ b/util/qemu-thread-posix.c
> > @@ -482,7 +482,6 @@ static void __attribute__((constructor)) qemu_thread_atexit_init(void)
> > }
> >
>
> More context:
>
> static bool name_threads;
>
> void qemu_thread_naming(bool enable)
> {
> name_threads = enable;
>
> #ifndef CONFIG_THREAD_SETNAME_BYTHREAD
> /* This is a debugging option, not fatal */
> if (enable) {
> fprintf(stderr, "qemu: thread naming not supported on this host\n");
> }
> #endif
> }
>
>
> >
> > -#ifdef CONFIG_PTHREAD_SETNAME_NP
>
> Why are we using CONFIG_THREAD_SETNAME_BYTHREAD in one place, and
> CONFIG_PTHREAD_SETNAME_NP in another?
>
> /me checks configure - oh:
>
> # Hold two types of flag:
> # CONFIG_THREAD_SETNAME_BYTHREAD - we've got a way of setting the name on
> # a thread we have a handle to
> # CONFIG_PTHREAD_SETNAME_NP - A way of doing it on a particular
> # platform
>
> even though, right now, we only either set both flags at once or leave
> both clear, since we don't (yet?) have any other platform-specific ways
> to do it.
It seems so. I'm not sure whether they could be useful in the future
and I'm fine with them, hence I keep it as is.
>
> > typedef struct {
> > void *(*start_routine)(void *);
> > void *arg;
> > @@ -498,13 +497,15 @@ static void *qemu_thread_start(void *args)
> > /* Attempt to set the threads name; note that this is for debug, so
> > * we're not going to fail if we can't set it.
> > */
> > - pthread_setname_np(pthread_self(), qemu_thread_args->name);
> > +#ifdef CONFIG_PTHREAD_SETNAME_NP
> > + if (qemu_thread_args->name) {
> > + pthread_setname_np(pthread_self(), qemu_thread_args->name);
>
> Post-patch, this (attempts to) set the thread name if a non-NULL name is
> present...
>
>
> >
> > -#ifdef CONFIG_PTHREAD_SETNAME_NP
> > - if (name_threads) {
> > - QemuThreadArgs *qemu_thread_args;
> > - qemu_thread_args = g_new0(QemuThreadArgs, 1);
> > - qemu_thread_args->name = g_strdup(name);
>
> ...but pre-patch, qemu_thread_args->name was left NULL unless
> name_threads was true, because someone had called
> qemu_thread_naming(true)...
>
> > - qemu_thread_args->start_routine = start_routine;
> > - qemu_thread_args->arg = arg;
> > -
> > - err = pthread_create(&thread->thread, &attr,
> > - qemu_thread_start, qemu_thread_args);
> > - } else
> > -#endif
> > - {
> > - err = pthread_create(&thread->thread, &attr,
> > - start_routine, arg);
> > - }
> > + qemu_thread_args = g_new0(QemuThreadArgs, 1);
> > + qemu_thread_args->name = g_strdup(name);
>
> ...so you have changed semantics - you are now unconditionally trying to
> set the thread name, instead of honoring qemu_thread_naming(). Do we
> still need qemu_thread_naming() (tied to opt debug-threads)?
>
> You need to either fix your code to remain conditional on whether
> name_threads is set, or document the semantic change as intentional in
> the commit message.
Indeed, thanks for catching that. What I really wanted is probably
this:
static void *qemu_thread_start(void *args)
{
...
#ifdef CONFIG_PTHREAD_SETNAME_NP
if (name_threads && qemu_thread_args->name) {
pthread_setname_np(pthread_self(), qemu_thread_args->name);
}
#endif
...
}
I'll fix that up in next version.
>
> However, the idea for refactoring to always use the shim makes sense.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2018-04-11 3:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 12:49 [Qemu-devel] [PATCH 0/2] qemu-thread: allow cur_mon be per thread Peter Xu
2018-04-10 12:49 ` [Qemu-devel] [PATCH 1/2] qemu-thread: always keep the posix wrapper layer Peter Xu
2018-04-10 13:35 ` Eric Blake
2018-04-11 3:18 ` Peter Xu [this message]
2018-04-10 12:49 ` [Qemu-devel] [PATCH 2/2] qemu-thread: let cur_mon be per-thread Peter Xu
2018-04-10 13:54 ` Eric Blake
2018-04-11 3:31 ` Peter Xu
2018-04-11 1:45 ` Stefan Hajnoczi
2018-04-11 3:49 ` Peter Xu
2018-04-11 9:23 ` Paolo Bonzini
2018-04-11 9:35 ` Peter Xu
2018-04-11 9:38 ` Paolo Bonzini
2018-04-11 9:48 ` Peter Xu
2018-04-11 13:06 ` Eric Blake
2018-04-12 5:24 ` Peter Xu
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=20180411031826.GA13887@xz-mi \
--to=peterx@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.
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).