> >> This suggests we are incorrectly coalescing writes, and we should
> >> actually be
> >> notifying qemu when (at least) he first write occurs. If we aren't
> >> outputting
> >> anything we don't want to be waking up periodically just to flush an
> >> empty
> >> MMIO buffer.
> >
> > That is com
On 06/08/2010 08:18 AM, Gerd Hoffmann wrote:
On 06/08/10 13:50, Paul Brook wrote:
Kill nographic timer. Have a global gui_timer instead. Have the gui
timer enabled unconditionally. We need a timer running anyway for
mmio
flush, so the whole have-gui-timer-only-when-needed logic is pretty
po
On 06/08/10 13:50, Paul Brook wrote:
Kill nographic timer. Have a global gui_timer instead. Have the gui
timer enabled unconditionally. We need a timer running anyway for mmio
flush, so the whole have-gui-timer-only-when-needed logic is pretty
pointless. It also simplifies displaylisteners co
> >> Kill nographic timer. Have a global gui_timer instead. Have the gui
> >> timer enabled unconditionally. We need a timer running anyway for mmio
> >> flush, so the whole have-gui-timer-only-when-needed logic is pretty
> >> pointless. It also simplifies displaylisteners coming and going at
>
On 06/07/10 18:12, Paul Brook wrote:
Kill nographic timer. Have a global gui_timer instead. Have the gui
timer enabled unconditionally. We need a timer running anyway for mmio
flush, so the whole have-gui-timer-only-when-needed logic is pretty
pointless. It also simplifies displaylisteners co
> Kill nographic timer. Have a global gui_timer instead. Have the gui
> timer enabled unconditionally. We need a timer running anyway for mmio
> flush, so the whole have-gui-timer-only-when-needed logic is pretty
> pointless. It also simplifies displaylisteners coming and going at
> runtime, we
