qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>, Brad <brad@comstyle.com>
Subject: Re: [Qemu-devel] getting rid of coroutine-gthread?
Date: Tue, 15 Jan 2013 14:28:33 +0100	[thread overview]
Message-ID: <50F55981.1050100@redhat.com> (raw)
In-Reply-To: <50F5572F.1010208@redhat.com>

Il 15/01/2013 14:18, Kevin Wolf ha scritto:
>> > Brad and Peter,
>> > 
>> > as far as I know OpenBSD and Linux/ARM were the main users of
>> > coroutine-gthread.  Do you think we could dump it and rely on
>> > coroutine-sigaltstack only?  The differences in signal handling of the
>> > gthread implementation always worried me.
>> > 
>> > What versions of OpenBSD would we have to drop support for?  Is that
>> > acceptable to you?
> Changing the defaults for these platforms may be a good idea, but I
> actually like the option of having coroutine-gthread because it's much
> friendlier to debug - gdb supports threads, but not coroutines.
> 
> Is coroutine-gthread blocking anything or is it just that you're not
> entirely confident in its correctness?

I'm not entirely confident in its correctness, and I'd be afraid of
breaking things when converting dataplane to AIOContext.

Paolo

  reply	other threads:[~2013-01-15 13:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 18:11 [Qemu-devel] getting rid of coroutine-gthread? Paolo Bonzini
2013-01-11 18:24 ` Andreas Färber
2013-01-12  9:07   ` Brad Smith
2013-01-12 12:08     ` Peter Maydell
2013-01-12 12:21       ` Brad Smith
2013-01-12  9:03 ` Brad Smith
2013-01-15 13:18 ` Kevin Wolf
2013-01-15 13:28   ` Paolo Bonzini [this message]
2013-01-15 13:40     ` Kevin Wolf
2013-01-15 15:13       ` Paolo Bonzini

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=50F55981.1050100@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=brad@comstyle.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 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).