qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org
Cc: yhalperi@redhat.com, kraxel@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Suspend (S3) support
Date: Mon, 20 Jun 2011 13:11:50 +0200	[thread overview]
Message-ID: <1308568312-5463-1-git-send-email-alevy@redhat.com> (raw)

The first patch is a slightly revised patch send before, introducing a
print helper (qxl_mode_to_string) that is used by the second patch too, hence
I'm sending them together. I've looked for additional places to use qxl_mode_to_string
like Gerd asked before, found just one.

The second patch is the one adding support for QXL_IO_UPDATE_MEM.

This is just part of the suspend support. It requires a revised spice-server
(to implement the update_mem io), and a revised driver (patches on spice-devel
for the windows driver, the linux to-be-done).

Alon Levy (2):
  qxl: interface_get_command: fix reported mode
  qxl: add QXL_IO_UPDATE_MEM for guest S3&S4 support

 hw/qxl.c |   47 ++++++++++++++++++++++++++++++++++++++++++++---
 1 files changed, 44 insertions(+), 3 deletions(-)

-- 
1.7.5.2

             reply	other threads:[~2011-06-20 11:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 11:11 Alon Levy [this message]
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
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=1308568312-5463-1-git-send-email-alevy@redhat.com \
    --to=alevy@redhat.com \
    --cc=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).