All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] versatile: Push lsi initialization to the end
Date: Mon, 08 Oct 2012 19:09:44 +0200	[thread overview]
Message-ID: <507308D8.2050609@siemens.com> (raw)
In-Reply-To: <20121008170720.GA9230@hall.aurel32.net>

On 2012-10-08 19:07, Aurelien Jarno wrote:
> 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.kiszka@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.

-nographic (-serial mon:stdio) + SCSI disk, at least that was the
combination here.

See http://thread.gmane.org/gmane.comp.emulators.qemu/174687 for a more
generic, well, workaround.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-10-08 17:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 17:30 [Qemu-devel] [PATCH] versatile: Push lsi initialization to the end Jan Kiszka
2012-10-05 17:42 ` Peter Maydell
2012-10-05 18:01   ` Jan Kiszka
2012-10-06  2:13     ` Peter Maydell
2012-10-08  6:52       ` Jan Kiszka
2012-10-08 15:18         ` Paolo Bonzini
2012-10-08 15:28           ` Jan Kiszka
2012-10-08 16:02             ` Peter Maydell
2012-10-08 16:28               ` Paolo Bonzini
2012-10-08 16:46                 ` Jan Kiszka
2012-10-08 17:07         ` Aurelien Jarno
2012-10-08 17:09           ` Jan Kiszka [this message]
2012-10-08 16:33 ` Peter Maydell
2012-10-08 16:39   ` Paolo Bonzini

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=507308D8.2050609@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=aurelien@aurel32.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.