From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: "Olivier Hainque" <hainque@adacore.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Ян Завадовский" <zavadovsky.yan@gmail.com>,
"Stefan Weil" <sw@weilnetz.de>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Fabien Chouteau" <chouteau@adacore.com>
Subject: Re: [Qemu-devel] [PATCH] thread-win32: fix GetThreadContext() permanently fails
Date: Tue, 23 Jun 2015 13:52:53 +0200 [thread overview]
Message-ID: <55894895.5050204@redhat.com> (raw)
In-Reply-To: <20150623114344.GF30318@redhat.com>
On 23/06/2015 13:43, Daniel P. Berrange wrote:
> > We can and should just reuse glib these days as much as we can (probably
> > not entirely because glib doesn't have detached threads). At least a
> > few years ago, winpthreads was much slower than native Win32, which is
> > why everyone reinvents the wheel.
>
> Are you sure that was wrt the (new) winpthreads library maintained by
> Mingw64 team, and not the confusingly similar pthreads-win32 library ?
None of them use native Win32 condition variables, which is the main
reason to switch to glib's version.
Paolo
next prev parent reply other threads:[~2015-06-23 11:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 21:54 [Qemu-devel] [PATCH] thread-win32: fix GetThreadContext() permanently fails Zavadovsky Yan
2015-06-23 6:02 ` Stefan Weil
2015-06-23 9:49 ` Fabien Chouteau
2015-06-23 10:11 ` Ян Завадовский
2015-06-23 9:55 ` Ян Завадовский
2015-06-23 10:30 ` Peter Maydell
2015-06-23 10:46 ` Paolo Bonzini
2015-06-23 11:18 ` Daniel P. Berrange
2015-06-23 11:32 ` Paolo Bonzini
2015-06-23 11:43 ` Daniel P. Berrange
2015-06-23 11:52 ` Paolo Bonzini [this message]
2015-06-23 11:23 ` Peter Maydell
2015-06-23 17:07 ` Stefan Weil
2015-06-24 9:09 ` Fabien Chouteau
2015-06-24 10:03 ` Peter Maydell
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=55894895.5050204@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=chouteau@adacore.com \
--cc=hainque@adacore.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=zavadovsky.yan@gmail.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).