From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] ioemu/qemu vga: save and restore vram buffer (revised)
Date: Mon, 17 Dec 2007 16:22:11 +0000 [thread overview]
Message-ID: <200712171622.12475.paul@codesourcery.com> (raw)
In-Reply-To: <18278.23285.98750.687170@mariner.uk.xensource.com>
> In any case, vl.c's saving arrangements do save the buffer in
> phys_ram_base - but that isn't what the guest sees in the VGA memory
It doesn't matter what the guest physical mappings (if any) are.
> area. The guest sees the vga memory-mapped IO registers (whose
> meaning _is_ generally saved by vga.c), plus it can use the VGA memory
> area and those control registers to access the whole of s->vram_ptr in
> a bank-switched way. And it is that whole VGA memory buffer which is
> `displayed' to (eg) vlc clients.
If you look closer, you'll find that s->vram_ptr actually points to an offset
from phys_ram_base. So the VGA framebuffer is already saved by ram_save.
If the xen patches have changed this then you may need your patch. It has no
business in mainstream qemu though.
Paul
next prev parent reply other threads:[~2007-12-17 16:23 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
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 [this message]
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=200712171622.12475.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=Ian.Jackson@eu.citrix.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).