qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH] versatile: Push lsi initialization to the end


From: Jan Kiszka
Subject: Re: [Qemu-devel] [PATCH] versatile: Push lsi initialization to the end
Date: Mon, 08 Oct 2012 18:46:18 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

On 2012-10-08 18:28, Paolo Bonzini wrote:
> Il 08/10/2012 18:02, Peter Maydell ha scritto:
>>>> It's not (only) about a missing event for the serial frontend, it's also
>>>> about a spurious open event to the monitor. That generates unwanted
>>>> output during startup.
>> Right, so whatever's sending that event needs not to do so until
>> creation of the machine is complete. Sending events randomly
>> halfway through init is a recipe for problems...
> 
> So we now have proof that using bottom halves outside the block layer
> was a bad idea.  Thanks Jan. :)
> 
> If Stefan goes on with the AioContext idea, we can have separate
> AioContexts for qemu_bh_new on one side and for block devices on the
> other, so that qemu_bh_new bottom halves won't fire just because
> something is calling the block layer.
> 
> In the meanwhile, qemu_char could use a QEMUTimer expiring in the past
> instead of a bottom half.

Sounds "beautiful", waiting to break when we leave like this and start
playing with the timer subsystem ;). But I guess it's best for now. Let
me have a look...

Jan

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



reply via email to

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