From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] iothread improvements for Mac OS X
Date: Sat, 23 Jul 2011 11:54:17 -0500 [thread overview]
Message-ID: <4E2AFCB9.8050606@codemonkey.ws> (raw)
In-Reply-To: <1307617825-17149-1-git-send-email-pbonzini@redhat.com>
On 06/09/2011 06:10 AM, Paolo Bonzini wrote:
> These are two old patches that I never submitted because I didn't really
> think they were useful except as cleanups. Recently, however, Alex Graf
> mentioned some problems that Mac OS X has with iothread, and they sounded
> to me like they were related to these patches. And quite surprisingly,
> both of them were fixing bugs!
>
> Mac OS X still has problems with iothread according to Alex's testing
> (Linux times out in libata, and reactos likewise hangs early on I/O),
> but at least the patches fix deadlocks and keep a responsive UI.
>
> Paolo Bonzini (2):
> iothread: replace fair_mutex with a condition variable
> qemu-timer: change unix timer to dynticks
>
Applied. Thanks.
Regards,
Anthony Liguori
> cpus.c | 24 +++++++++---------------
> qemu-timer.c | 40 ++++++++++++++++++++++++++++------------
> 2 files changed, 37 insertions(+), 27 deletions(-)
>
prev parent reply other threads:[~2011-07-23 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 11:10 [Qemu-devel] [PATCH 0/2] iothread improvements for Mac OS X Paolo Bonzini
2011-06-09 11:10 ` [Qemu-devel] [PATCH 1/2] iothread: replace fair_mutex with a condition variable Paolo Bonzini
2011-06-09 11:10 ` [Qemu-devel] [PATCH 2/2] qemu-timer: change unix timer to dynticks Paolo Bonzini
2011-06-27 14:07 ` [Qemu-devel] [PATCH 0/2] iothread improvements for Mac OS X Paolo Bonzini
2011-06-29 4:26 ` Alexandre Raymond
2011-07-23 16:54 ` Anthony Liguori [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=4E2AFCB9.8050606@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=pbonzini@redhat.com \
--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.