From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v4 0/6] save/restore on Xen Date: Tue, 24 Jan 2012 17:48:10 +0200 Message-ID: <4F1ED2BA.5050505@redhat.com> References: <4F19AB66.8060901@siemens.com> <4F1D4974.4090003@siemens.com> <4F1D4E43.7000501@siemens.com> <4F1D80BA.1040504@siemens.com> <4F1D9546.4040801@siemens.com> <4F1D9649.1000102@codemonkey.ws> <4F1E91AF.9040402@redhat.com> <4F1E959F.4060001@redhat.com> <4F1E96BA.40801@redhat.com> <4F1E99B6.7010709@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F1E99B6.7010709@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Paolo Bonzini Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini , Jan Kiszka , "qemu-devel@nongnu.org" , Gerd Hoffmann List-Id: xen-devel@lists.xenproject.org On 01/24/2012 01:44 PM, Paolo Bonzini wrote: > 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. :) Based on the testing, it does not. -- error compiling committee.c: too many arguments to function