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 <jan.kis...@siemens.com> 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 aurel...@aurel32.net http://www.aurel32.net
