From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1.1] coroutine: Avoid ucontext usage on i386 Linux host
Date: Thu, 10 May 2012 00:04:57 +0400 [thread overview]
Message-ID: <4FAACDE9.9080607@msgid.tls.msk.ru> (raw)
In-Reply-To: <4FAAC3A3.5040503@siemens.com>
On 09.05.2012 23:21, Jan Kiszka wrote:
[]
> --- a/configure
> +++ b/configure
> @@ -2777,17 +2777,22 @@ fi
> # windows autodetected by make
> if test "$coroutine" = "" -o "$coroutine" = "ucontext"; then
> if test "$darwin" != "yes"; then
> - cat > $TMPC << EOF
> + if test "$linux" = "yes" -a "$cpu" = "i386"; then
> + # RT signal mask corruption for 32-on-64 bit prevents ucontext usage
> + coroutine_backend=gthread
> + else
I'd say this is unacceptable. We're making 32bit x86 code to use
different implementation of one of core subsystems, and 32bit code
already receives much less testing because everyone is using 64bit
code and many don't care about 32bits (this is general 32bit case,
not a more exotic 32-on-64bit case). I think it is a sure way to
have more subtle "works for me" bugs which happens only on 32bits..
Besides, gthread is quite a bit slower than ucontext (but at least
it works even in the exotic case).
Thanks,
/mjt
prev parent reply other threads:[~2012-05-09 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 19:21 [Qemu-devel] [PATCH 1.1] coroutine: Avoid ucontext usage on i386 Linux host Jan Kiszka
2012-05-09 19:27 ` Michael Tokarev
2012-05-09 19:34 ` Jan Kiszka
2012-05-09 19:48 ` Anthony Liguori
2012-05-09 19:57 ` Jan Kiszka
2012-05-09 20:01 ` Anthony Liguori
2012-05-09 20:11 ` Jan Kiszka
2012-05-09 20:46 ` Peter Maydell
2012-05-09 20:59 ` Anthony Liguori
2012-05-09 21:27 ` Peter Maydell
2012-05-09 21:36 ` Anthony Liguori
2012-05-09 20:56 ` Anthony Liguori
2012-05-09 20:04 ` Michael Tokarev [this message]
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=4FAACDE9.9080607@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kwolf@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.