From: Gerd Hoffmann <kraxel@redhat.com>
To: yhalperi <yhalperi@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] qxl: add QXL_IO_UPDATE_MEM for guest S3&S4 support
Date: Wed, 29 Jun 2011 12:25:00 +0200 [thread overview]
Message-ID: <4E0AFD7C.2050209@redhat.com> (raw)
In-Reply-To: <20110629092133.GL30873@bow.redhat.com>
On 06/29/11 11:21, Alon Levy wrote:
> On Wed, Jun 29, 2011 at 11:01:11AM +0200, Gerd Hoffmann wrote:
>> Hi,
>>
>>>> I think it will receive them after migration, since the command ring
>>>> was stored.
>>> Our confusion here is because you think there is still seemless migration. Unfortunately
>>> it doesn't work right now, unless you plan to fix it the only form of migration right
>>> now is switch-host, and for that those commands will be lost, the new connection will receive
>>> images for each surface. If you treat the client as seemless you are completely right.
>>
>> The spice server needs this too so it can render the surfaces
>> correctly before sending the surface images to the client (or send
>> the old surfaces and the commands on top of that).
>>
>> That is one difference between qemu migration and S3 state: For qemu
>> migration it is no problem to have unprocessed commands in the
>> rings, they will simply be processed once the spice server state is
>> restored. When the guest driver restores the state when it comes
>> back from S3 it needs the command rings to do so, thats why they
>> must be flushed before entering S3 ...
>
> You mean it needs the command rings to be empty before, since they are lost
> during the reset, right?
One more reason. Wasn't aware there is a reset anyway, was thinking
more about the command ordering. Without reset spice-server would first
process the old commands (which may reference non-existing surfaces),
then the new commands which re-recreate all state, which is simply the
wrong order. With reset the old commands just get lost which causes
rendering bugs.
Is it an option to have the driver just remove the commands from the
ring (and resubmit after resume)? I suspect it isn't as there is no
race-free way to do that, right?
cheers,
Gerd
next prev parent reply other threads:[~2011-06-29 10:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 11:11 [Qemu-devel] [PATCH 0/2] Suspend (S3) support Alon Levy
2011-06-20 11:11 ` [Qemu-devel] [PATCH 1/2] qxl: interface_get_command: fix reported mode Alon Levy
2011-06-20 11:11 ` [Qemu-devel] [PATCH 2/2] qxl: add QXL_IO_UPDATE_MEM for guest S3&S4 support Alon Levy
2011-06-20 12:13 ` Gerd Hoffmann
2011-06-20 12:57 ` Alon Levy
2011-06-20 12:58 ` Alon Levy
2011-06-20 14:07 ` Gerd Hoffmann
2011-06-20 15:11 ` Alon Levy
2011-06-20 15:48 ` Alon Levy
2011-06-20 15:50 ` Gerd Hoffmann
2011-06-20 16:32 ` Alon Levy
2011-06-20 20:53 ` Alon Levy
2011-06-21 6:29 ` Yonit Halperin
2011-06-22 9:13 ` Gerd Hoffmann
2011-06-22 9:57 ` Alon Levy
2011-06-26 16:59 ` Yonit Halperin
2011-06-26 17:47 ` Alon Levy
2011-06-27 6:28 ` yhalperi
2011-06-27 8:16 ` Alon Levy
2011-06-27 8:25 ` yhalperi
2011-06-27 9:20 ` Alon Levy
2011-06-29 9:01 ` Gerd Hoffmann
2011-06-29 9:21 ` Alon Levy
2011-06-29 10:25 ` Gerd Hoffmann [this message]
2011-06-29 11:38 ` Alon Levy
2011-06-30 10:26 ` Yonit Halperin
2011-06-30 10:46 ` Gerd Hoffmann
2011-06-30 11:41 ` Alon Levy
2011-06-30 12:12 ` Gerd Hoffmann
2011-06-30 12:50 ` Alon Levy
2011-06-30 13:17 ` Gerd Hoffmann
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=4E0AFD7C.2050209@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yhalperi@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).