[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] main: force enabling of I/O thread

From: Anthony Liguori
Subject: Re: [Qemu-devel] [PATCH] main: force enabling of I/O thread
Date: Fri, 02 Sep 2011 09:31:28 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10

On 09/01/2011 01:31 PM, Andreas Färber wrote:
Am 30.08.2011 um 21:28 schrieb Anthony Liguori:

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.

My problem is that at HEAD *none* of the i386,ppc,sparc guests that used
to work about a month ago boot *at all* on my Darwin/ppc64 host.

Might be TCG, might be the new MemoryRegion API, might be (non-)I/O
thread. Means a lot of git history testing despite little time. An
ultimatum to make things even worse doesn't really help there... ;)

For a platform to be supported, it needs to be actively maintained and fixed. If there aren't enough folks testing/fixing Darwin/ppc64, then it's not a platform we can reasonable support :-/


Anthony Liguori


reply via email to

[Prev in Thread] Current Thread [Next in Thread]