From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52275 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OC9ph-00027O-Rx for qemu-devel@nongnu.org; Wed, 12 May 2010 07:10:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OC5bq-0002M3-7d for qemu-devel@nongnu.org; Wed, 12 May 2010 02:40:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:3972) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OC5bo-0002Lc-SD for qemu-devel@nongnu.org; Wed, 12 May 2010 02:39:58 -0400 Message-ID: <4BEA4D36.3020608@redhat.com> Date: Wed, 12 May 2010 09:39:50 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: QEMU-KVM and video performance References: <4BCEBE5C.4020404@redhat.com> <20100421183357.GK27575@shareable.org> <4BCF6699.2060201@redhat.com> <4BCFF4B5.7010302@redhat.com> <4BE7B6A9.8060007@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerhard Wiesinger Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org On 05/12/2010 09:14 AM, Gerhard Wiesinger wrote: > On Mon, 10 May 2010, Avi Kivity wrote: > >> On 05/09/2010 10:35 PM, Gerhard Wiesinger wrote: >>>>> >> >> For 256 color more the first priority is to find out why direct >> mapping is not used. I'd suggest tracing the code that makes this >> decision (in hw/*vga.c) and seeing if it's right or not. > > I think this is because A000 is not initialized for KVM (see log below > and logging patch attached). Why isn't it initialized? Did the guest configure things such as it is impossible to map it directly? Or does the configuration allow direct mapping and qemu incorrectly decides that it cannot direct map? Best would be to print out all the configuration registers and interpret them according to the specification. > > vga_dirty_log_start > vga_dirty_log_start_mapping_lfb_vram_mapped, start=0x000A0000, > len=0x00008000 > BUG: kvm_dirty_pages_log_change: invalid parameters > 00000000000a0000-00000000000a7fff Why does this happen? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.