From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Bug in protected mode segments? Date: Wed, 22 Oct 2008 12:48:04 -0500 Message-ID: <48FF6754.5040406@codemonkey.ws> References: <48FF6512.5010202@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Mathias Gottschlag Return-path: Received: from el-out-1112.google.com ([209.85.162.182]:31383 "EHLO el-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759549AbYJVRsK (ORCPT ); Wed, 22 Oct 2008 13:48:10 -0400 Received: by el-out-1112.google.com with SMTP id z25so773713ele.1 for ; Wed, 22 Oct 2008 10:48:07 -0700 (PDT) In-Reply-To: <48FF6512.5010202@web.de> Sender: kvm-owner@vger.kernel.org List-ID: Mathias Gottschlag wrote: > I am currently working on my own hobby kernel and tested it on kvm > today. I think I found a bug in kvm with it (already discussed it on > IRC): > > I wanted my kernel to be at a higher virtual address, in my case > 0xE0000000. To get it there (Grub loaded it at physical addr > 0x100000), I followed the steps at > http://wiki.osdev.org/Higher_Half_With_GDT: > > Grub inits the CPU with no paging and flat segmenting, I now activate > segments to move the code to 0xE0000000 and later activate paging and > reset the segments. When I run this code on qemu or on real hardware > (Athlon XP), everything works well, but on kvm I get several hangs. > For example I try to write to 0xE00B8000 to write into the VGA > framebuffer. This addres should now get translated back to 0xB8000 by > the segment which has the base address 0x20000000, and this definately > works on real hardware, but on kvm I only notice a hang at the > instruction which writes at that address (kvm still responds, but > doesn't update eip anymore, execution stops. I looked briefly and there didn't appear to be any explicit checks for wrap around but I think that it will work correctly since we're always using at least unsigned long in the host. My suspicion is that we're somehow getting something wrong with MMIO decoding. Regards, Anthony Liguori > Someone on IRC told me that this might be because address wrapping > isn't implemented properly (this could have been unnoticed until now > as no real OS uses such weird segmenting). > > You can try it out yourself using the code at > http://wiki.osdev.org/Higher_Half_With_GDT, this code will work for > example in qemu, but not in kvm. I attached a version including a > build script and a script to create the floppy image (you only need > gcc, nasm and grub, type in "sh build.sh" and you get your image) for > testing. It should show "Hello world" on a machine where it runs > correctly. > > Mathias Gottschlag > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html