From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [6989] Fix display breakage when resizing the screen (v2) (Avi Kivity)
Date: Mon, 06 Apr 2009 18:35:58 +0100 [thread overview]
Message-ID: <49DA3D7E.5050506@eu.citrix.com> (raw)
In-Reply-To: <49DA176B.4090102@redhat.com>
Avi Kivity wrote:
> Avi Kivity wrote:
>>> Secondly it doesn't follow the basic idea behind the DisplayState
>>> surface: it is supposed to be a pixel surface provided by the vga
>>> emulator to the frontends, cirrus shouldn't have to care what size it
>>> is.
>>> In fact cirrus emulates bitblit operations on the emulated framebuffer,
>>> not on the DisplayState surface; if it does so is a bug and should be
>>> fixed.
>>>
>> This happens through cirrus_do_copy(), which implies that the display
>> surface is involved. Is that wrong?
>
> I think what you're saying is, we shouldn't call qemu_console_copy() in
> cirrus_do_copy() if vga is not displayed on the console?
>
> (and conversely, if it is displayed, we shouldn't call
> cirrus_invalidate_region).
>
I tried several times to manually reproduce the issue with no luck: if
no vnc clients are supposed to be connected, how do you make the cirrus
emulated hw do a bitblit?
In any case it makes sense that the problem is in qemu_console_copy()
rather than in the rop function itself that only operates on the
emulated framebuffer.
But calling qemu_console_copy() in cirrus_do_copy() shouldn't be risky
because before that, we call vga_hw_update() that should do the resize.
Without a better understanding of the bug I will refrain from making any
suggestion.
next prev parent reply other threads:[~2009-04-06 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 18:41 [Qemu-devel] [6989] Fix display breakage when resizing the screen (v2) (Avi Kivity) Anthony Liguori
2009-04-06 14:21 ` Stefano Stabellini
2009-04-06 14:29 ` Anthony Liguori
2009-04-06 14:33 ` Stefano Stabellini
2009-04-06 14:44 ` Avi Kivity
2009-04-07 1:44 ` Ryan Harper
2009-04-07 9:28 ` Avi Kivity
2009-04-07 9:32 ` Stefano Stabellini
2009-04-06 14:41 ` Avi Kivity
2009-04-06 14:53 ` Avi Kivity
2009-04-06 17:35 ` Stefano Stabellini [this message]
2009-04-06 17:46 ` Avi Kivity
2009-04-06 18:01 ` Stefano Stabellini
2009-04-06 18:32 ` Avi Kivity
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=49DA3D7E.5050506@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--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.