From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] fix -kernel option Date: Sun, 09 Dec 2007 10:54:04 +0200 Message-ID: <475BAD2C.1040404@qumranet.com> References: <11970469043041-git-send-email-gcosta@redhat.com> <47597F62.6060600@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Glauber de Oliveira Costa To: Anthony Liguori Return-path: In-Reply-To: <47597F62.6060600-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Anthony Liguori wrote: > Glauber de Oliveira Costa wrote: > >> Currently, the -kernel option is not working. >> >> Reason is, because we're registering chunks for regions 0-0xa0000 and >> 0x100000-ram_size, the phys_ram_addr + PA is broken. >> >> > > I think this patch is a reasonable work-around but the long term > solution is probably going to have to be making sure that nothing makes > the phys_ram_addr + PA assumption. With > 4GB of memory, this > assumption is broken because of the BIOS/PCI holes anyway. I guess we > could preserve this assumption though by burning some memory. > > We don't need to burn the memory, you can munmap() the unneeded part after allocating it. Just make sure you don't touch it afterwards. We used this method in previous versions, then moved to the current approach which is more aligned with how qemu does things. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php