All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael W. Bombardieri" <mb@ii.net>
Cc: Stefan Weil <sw@weilnetz.de>, Prashant Satish <ps@omledom.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] broken win32 coroutines (was Re: qemu 1.6.1)
Date: Tue, 24 Jun 2014 07:22:59 +0200	[thread overview]
Message-ID: <53A90B33.1000306@redhat.com> (raw)
In-Reply-To: <20140624014103.GA606@bom.nom.co>

Il 24/06/2014 03:41, Michael W. Bombardieri ha scritto:
> Hi,
>
> Thanks for adding me to this thread.
> I am not familiar with the qemu source code but I am aware
> of the coroutine crash and I can test a patch if you have
> one.
>
> qemu 1.5.1 was the last version I was able to build and use
> on win32. Later versions build without error but exhibit the
> coroutine crash.
> qemu binaries built with the coroutine feature disabled are
> to slow to use.

Peter posted one here:

http://article.gmane.org/gmane.comp.emulators.qemu/282189/raw

Paolo

  reply	other threads:[~2014-06-24  5:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23  7:39 [Qemu-devel] qemu 1.6.1 Michael W. Bombardieri
2013-10-23  9:00 ` Paolo Bonzini
2013-10-23 20:26   ` Stefan Weil
2013-10-24 10:38     ` Paolo Bonzini
2013-10-24 16:37       ` Stefan Weil
2013-10-24 21:47         ` Paolo Bonzini
2013-10-26  9:51           ` Stefan Weil
2013-10-27  6:54             ` Paolo Bonzini
2013-10-27 10:44               ` Stefan Weil
2013-10-27 15:38               ` Stefan Weil
2014-06-23 14:39             ` [Qemu-devel] broken win32 coroutines (was Re: qemu 1.6.1) Paolo Bonzini
2014-06-24  1:41               ` Michael W. Bombardieri
2014-06-24  5:22                 ` Paolo Bonzini [this message]
2014-06-25  6:48                   ` Michael W. Bombardieri

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=53A90B33.1000306@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=mb@ii.net \
    --cc=ps@omledom.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    /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.