From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org, yhalperi@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] qxl: add QXL_IO_UPDATE_MEM for guest S3&S4 support
Date: Wed, 22 Jun 2011 11:13:19 +0200 [thread overview]
Message-ID: <4E01B22F.3020702@redhat.com> (raw)
In-Reply-To: <20110620163230.GG28412@bow.redhat.com>
Hi,
>> worker call. We can add a I/O command to ask qxl to push the
>> release queue head to the release ring.
>
> So you suggest to replace QXL_IO_UPDATE_MEM with what, two io commands instead
> of using the val parameter?
I'd like to (a) avoid updating the libspice-server API if possible and
(b) have one I/O command for each logical step. So going into S3 could
look like this:
(0) stop putting new commands into the rings
(1) QXL_IO_NOTIFY_CMD
(2) QXL_IO_NOTIFY_CURSOR
qxl calls notify(), to make the worker thread empty the command
rings before it processes the next dispatcher request.
(3) QXl_IO_FLUSH_SURFACES (to be implemented)
qxl calls stop()+start(), spice-server renders all surfaces,
thereby flushing state to device memory.
(4) QXL_IO_DESTROY_ALL_SURFACES
zap surfaces
(5) QXL_IO_FLUSH_RELEASE (to be implemented)
push release queue head into the release ring, so the guest
will see it and can release everything.
(1)+(2)+(4) exist already.
(3)+(5) can be done without libspice-server changes.
Looks workable?
cheers,
Gerd
next prev parent reply other threads:[~2011-06-22 9:13 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 [this message]
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
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=4E01B22F.3020702@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 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.