From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Alexandre Raymond" <cerbere@gmail.com>,
"qemu-devel Developers" <qemu-devel@nongnu.org>,
"Blue Swirl" <blauwirbel@gmail.com>,
"Andreas Färber" <andreas.faerber@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 00:42:03 +0200 [thread overview]
Message-ID: <4E5C15BB.5080000@web.de> (raw)
In-Reply-To: <4E5C03CC.3010707@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
On 2011-08-29 23:25, Anthony Liguori wrote:
> On 08/29/2011 04:23 PM, Andreas Färber wrote:
>> Am 29.08.2011 um 22:24 schrieb Anthony Liguori:
>>
>>> On 08/29/2011 03:21 PM, Andreas Färber wrote:
>>>> Am 29.08.2011 um 20:03 schrieb Anthony Liguori:
>>>>
>>>>> On 08/22/2011 08:35 AM, Jan Kiszka wrote:
>>>>>> On 2011-08-22 15:24, Anthony Liguori wrote:
>>>>>>> Enabling the I/O thread by default seems like an important part of
>>>>>>> declaring
>>>>>>> 1.0.
>>>>>
>>>>> Given that [1] has been applied now, is there any objections to this
>>>>> patch?
>>>>
>>>> There had been additional patches to fix I/O thread issues on Darwin,
>>>> have any such fixes been applied the last few weeks?
>>>
>>> I don't see any outstanding Darwin patches in my queue so either they
>>> were applied or there were issues with them.
>>
>> Alexandre recalled his series on July 25, I spot neither explanation of
>> what was wrong with it nor a v2. Hope he'll explain.
>
> If there's uncertainty, I'd prefer to enable it sooner than later. This
> is a key 1.0 feature IMHO and I'd prefer to have more time to work
> through any issues.
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.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-08-29 22:42 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 [this message]
2011-08-30 18:45 ` Andreas Färber
2011-08-30 19:28 ` Anthony Liguori
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=4E5C15BB.5080000@web.de \
--to=jan.kiszka@web.de \
--cc=alex@csgraf.de \
--cc=andreas.faerber@web.de \
--cc=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=cerbere@gmail.com \
--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).