From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com
Subject: Re: [Qemu-devel] [PATCH] ioemu/qemu vga: save and restore vram buffer
Date: Mon, 10 Dec 2007 20:03:35 +0100 [thread overview]
Message-ID: <fb249edb0712101103y5409e2acnfda8a199883acae@mail.gmail.com> (raw)
In-Reply-To: <18269.33299.414015.995882@mariner.uk.xensource.com>
On 10/12/2007, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> The existing stdvga driver from xen-unstable tools/ioemu/hw/vga* does
> not save the emulated VGA memory contents. The symptoms include video
> malfunction after restore, including black screen (which can often be
> fixed by asking the guest to redraw) but also missing font setup etc.
> The attached patch fixes this by saving the entire VGA memory buffer,
> just like the Xen ioemu Cirrus emulator does.
Sounds reasonable.
>
> I have reinterpreted the `is_vbe' byte, which is related to
> CONFIG_BOCHS_VBE, as a general flags word. This enables my code to
> allow old images to be restored (albeit with loss of VGA memory), by
> using another bit in that word to indicate whether the VGA memory dump
> is present.
You can use the version_id parameter for that. Increase the value
passed to register_savevm and load the vram only if version_id >= 2.
Regards
next prev parent reply other threads:[~2007-12-10 19:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 18:14 [Qemu-devel] [PATCH] ioemu/qemu vga: save and restore vram buffer Ian Jackson
2007-12-10 19:03 ` andrzej zaborowski [this message]
2007-12-12 11:44 ` [Qemu-devel] [PATCH] ioemu/qemu vga: save and restore vram buffer (revised) Ian Jackson
2007-12-16 11:35 ` andrzej zaborowski
2007-12-17 11:18 ` Ian Jackson
2007-12-17 16:22 ` Paul Brook
2007-12-17 18:25 ` [Qemu-devel] xen / qemu convergence ? Ian Jackson
2007-12-17 18:52 ` andrzej zaborowski
2007-12-18 10:41 ` Ian Jackson
2007-12-17 18:55 ` Paul Brook
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=fb249edb0712101103y5409e2acnfda8a199883acae@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.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).