From: Paolo Bonzini <pbonzini@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/6] save/restore on Xen
Date: Tue, 24 Jan 2012 12:44:54 +0100 [thread overview]
Message-ID: <4F1E99B6.7010709@redhat.com> (raw)
In-Reply-To: <4F1E96BA.40801@redhat.com>
On 01/24/2012 12:32 PM, Avi Kivity wrote:
>> > Clearing the screen should only write to the RAM at 0xB8000 (and
>> > perhaps 0xA0000 since IIRC it's where text-mode fonts lie). The
>> > option ROM cannot even assume that the main BIOS knows about the VESA
>> > framebuffer, can it?
> Yes, but why should anything else be needed?
>
> When you switch to a graphics mode, clear as much of the framebuffer as
> you need.
Based on the comments, Windows apparently disagrees. :)
Paolo
next prev parent reply other threads:[~2012-01-24 11:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 17:20 [Qemu-devel] [PATCH v4 0/6] save/restore on Xen Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 1/6] vl.c: do not save the RAM state when Xen is enabled Stefano Stabellini
2012-01-23 15:58 ` Anthony Liguori
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 2/6] xen mapcache: check if memory region has moved Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 3/6] Set runstate to INMIGRATE earlier Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 4/6] cirrus_vga: do not reset videoram on resume Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 5/6] xen: record physmap changes to xenstore Stefano Stabellini
2012-01-20 17:21 ` [Qemu-devel] [PATCH v4 6/6] xen: change memory access behavior during migration Stefano Stabellini
2012-01-20 17:59 ` [Qemu-devel] [PATCH v4 0/6] save/restore on Xen Jan Kiszka
2012-01-23 10:47 ` Stefano Stabellini
2012-01-23 11:50 ` Jan Kiszka
2012-01-23 11:59 ` Stefano Stabellini
2012-01-23 12:10 ` Jan Kiszka
2012-01-23 14:46 ` Stefano Stabellini
2012-01-23 15:46 ` Jan Kiszka
2012-01-23 16:16 ` Stefano Stabellini
2012-01-23 16:22 ` Anthony Liguori
2012-01-23 17:13 ` Jan Kiszka
2012-01-23 17:18 ` Anthony Liguori
2012-01-23 17:31 ` Jan Kiszka
2012-01-23 17:36 ` Anthony Liguori
2012-01-24 10:21 ` Gerd Hoffmann
2012-01-24 11:13 ` Avi Kivity
2012-01-24 12:00 ` Stefano Stabellini
2012-01-24 15:39 ` Avi Kivity
2012-01-24 13:18 ` Anthony Liguori
2012-01-24 15:43 ` Avi Kivity
2012-01-24 13:25 ` Anthony Liguori
2012-01-24 15:47 ` Avi Kivity
2012-01-24 11:10 ` Avi Kivity
2012-01-24 11:27 ` Paolo Bonzini
2012-01-24 11:32 ` Avi Kivity
2012-01-24 11:44 ` Paolo Bonzini [this message]
2012-01-24 15:48 ` Avi Kivity
2012-01-24 11:52 ` Stefano Stabellini
2012-01-24 13:15 ` Anthony Liguori
2012-01-24 13:14 ` Anthony Liguori
2012-01-24 15:56 ` Avi Kivity
2012-01-24 17:51 ` Anthony Liguori
2012-01-23 16:00 ` Anthony Liguori
2012-01-23 16:46 ` Stefano Stabellini
2012-01-23 16:54 ` Anthony Liguori
2012-01-23 17:05 ` Stefano Stabellini
2012-01-23 17:07 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2012-01-25 13:04 Stefano Stabellini
2012-01-31 15:50 ` Stefano Stabellini
2012-02-13 12:20 ` Stefano Stabellini
2012-02-21 10:22 ` Stefano Stabellini
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=4F1E99B6.7010709@redhat.com \
--to=pbonzini@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--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).