From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Alexandre Raymond <cerbere@gmail.com>,
qemu-devel Developers <qemu-devel@nongnu.org>,
Blue Swirl <blauwirbel@gmail.com>, Jan Kiszka <jan.kiszka@web.de>,
Alexander Graf <alex@csgraf.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] main: force enabling of I/O thread
Date: Tue, 30 Aug 2011 14:28:21 -0500 [thread overview]
Message-ID: <4E5D39D5.3000507@codemonkey.ws> (raw)
In-Reply-To: <3345DE92-DEDA-4716-929D-8046E0EA2A00@web.de>
On 08/30/2011 01:45 PM, Andreas Färber wrote:
> Am 30.08.2011 um 00:42 schrieb Jan Kiszka:
>
>> What about making --enable-io-thread default as an intermediate step?
>> That would leave --disable-io-thread as temporary workaround until all
>> issues are fixed. The latter could generate a big fat warning that this
>> mode will be removed before 1.0.
>
> Yes please, that proposal sounds much better.
>
> If http://wiki.qemu.org/Planning/1.0 is still up-to-date, we have about
> six weeks to make I/O thread work everywhere.
I'm not a big fan of just flipping the configure flag. There is other
work being held up by disable-io-thread like the timer conversion.
If there aren't known issues, then I want to remove the non-I/O thread
code. git history is still there for anyone that wants to test w/o it.
Regards,
Anthony Liguori
>
> Andreas
next prev parent reply other threads:[~2011-08-30 19:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 13:24 [Qemu-devel] [PATCH] main: force enabling of I/O thread Anthony Liguori
2011-08-22 13:35 ` Jan Kiszka
2011-08-22 13:43 ` Anthony Liguori
2011-08-29 18:03 ` Anthony Liguori
2011-08-29 20:21 ` Andreas Färber
2011-08-29 20:24 ` Anthony Liguori
2011-08-29 21:23 ` Andreas Färber
2011-08-29 21:25 ` Anthony Liguori
2011-08-29 22:42 ` Jan Kiszka
2011-08-30 18:45 ` Andreas Färber
2011-08-30 19:28 ` Anthony Liguori [this message]
2011-09-01 18:31 ` Andreas Färber
2011-09-02 13:59 ` Mark Cave-Ayland
2011-09-02 14:31 ` Anthony Liguori
2011-09-02 14:42 ` Paolo Bonzini
2011-09-02 15:41 ` Anthony Liguori
2011-08-22 13:50 ` Peter Maydell
2011-08-22 14:00 ` Paolo Bonzini
2011-08-22 14:08 ` Jan Kiszka
2011-08-22 14:18 ` Peter Maydell
2011-08-22 14:09 ` Anthony Liguori
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=4E5D39D5.3000507@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alex@csgraf.de \
--cc=andreas.faerber@web.de \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=cerbere@gmail.com \
--cc=jan.kiszka@web.de \
--cc=pbonzini@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).