All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, mst@redhat.com, jan.kiszka@siemens.com
Subject: [Qemu-devel] Ping: [PATCH 0/1] configure time fix for thread naming on old glibc
Date: Wed, 26 Mar 2014 17:51:01 +0000	[thread overview]
Message-ID: <20140326175101.GI2504@work-vm> (raw)
In-Reply-To: <1394624898-2730-1-git-send-email-dgilbert@redhat.com>

* Dr. David Alan Gilbert (git) (dgilbert@redhat.com) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> Peter was preferring configure time detection of pthread_setname_np
> to guard against my recent breaking of builds on old libc.
> 
> I've tested this on:
>    Fedora 20 - modern glibc - works as before
>    RHEL 5 - glibc 2.5:
>      [dgilbert@davidgil-rhel5 try]$ ./bin/qemu-system-x86_64 -nographic -name debug-threads=on
>      qemu: thread naming not supported on this host
> 
>    and checked a mingw windows cross build builds.
> 
> A check on SLES11 is probably worth a try if someone has one to hand.
> 
> Dr. David Alan Gilbert (1):
>   Detect pthread_setname_np at configure time
> 
>  configure                | 28 ++++++++++++++++++++++++++++
>  util/qemu-thread-posix.c | 21 ++++++++++++++++++---
>  util/qemu-thread-win32.c |  2 ++
>  3 files changed, 48 insertions(+), 3 deletions(-)
> 
> -- 
> 1.8.5.3
> 
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  parent reply	other threads:[~2014-03-26 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 11:48 [Qemu-devel] [PATCH 0/1] configure time fix for thread naming on old glibc Dr. David Alan Gilbert (git)
2014-03-12 11:48 ` [Qemu-devel] [PATCH 1/1] Detect pthread_setname_np at configure time Dr. David Alan Gilbert (git)
2014-03-26 17:51 ` Dr. David Alan Gilbert [this message]
2014-03-27  7:20 ` [Qemu-devel] [PATCH 0/1] configure time fix for thread naming on old glibc Michael S. Tsirkin

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=20140326175101.GI2504@work-vm \
    --to=dgilbert@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.