From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60027) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TLGng-0007Bf-Kr for qemu-devel@nongnu.org; Mon, 08 Oct 2012 13:07:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TLGnb-0004iA-S8 for qemu-devel@nongnu.org; Mon, 08 Oct 2012 13:07:28 -0400 Received: from hall.aurel32.net ([88.191.126.93]:33297) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TLGnb-0004hx-Lr for qemu-devel@nongnu.org; Mon, 08 Oct 2012 13:07:23 -0400 Date: Mon, 8 Oct 2012 19:07:20 +0200 From: Aurelien Jarno Message-ID: <20121008170720.GA9230@hall.aurel32.net> References: <506F1934.5000002@siemens.com> <506F207A.70805@siemens.com> <5072782E.9090707@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <5072782E.9090707@siemens.com> Sender: Aurelien Jarno Subject: Re: [Qemu-devel] [PATCH] versatile: Push lsi initialization to the end List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Peter Maydell , qemu-devel On Mon, Oct 08, 2012 at 08:52:30AM +0200, Jan Kiszka wrote: > On 2012-10-06 04:13, Peter Maydell wrote: > > On 5 October 2012 19:01, Jan Kiszka wrote: > >> I'm not a fan of this either, but the alternatives are way more > >> complicated. We either need to rewrite the chardev subsystem, > >> specifically how mux'ed devices are registered and how the active one is > >> selected. Or we need to avoid flushing "unrelated" BHs for block > >> devices. Not sure of those read requests can be postponed. > > > > Is this a regression? If it is then the obvious answer is to back > > out whatever broke it... > > I'm using this machine for the first time, so I cannot answer this from > the top of my head. However, I don't think it can be a regression. > What is the bug exactly? Outputting the monitor prompt when using -nographic? If it is the case, please note that mips/mipsel is also affected. IIRC it appears somewhere between 1.1 and 1.2. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurelien@aurel32.net http://www.aurel32.net