From mboxrd@z Thu Jan 1 00:00:00 1970 From: cody Subject: Re: The way of mapping BIOS into the guest's address space Date: Tue, 14 Feb 2012 22:57:04 +0800 Message-ID: <4F3A7640.4060708@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: penberg@kernel.org, kvm@vger.kernel.org To: Yang Bai Return-path: Received: from mail-gx0-f174.google.com ([209.85.161.174]:64200 "EHLO mail-gx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753855Ab2BNO5z (ORCPT ); Tue, 14 Feb 2012 09:57:55 -0500 Received: by ggnh1 with SMTP id h1so24691ggn.19 for ; Tue, 14 Feb 2012 06:57:54 -0800 (PST) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 02/14/2012 07:03 PM, Yang Bai wrote: > Hi all, > > Since on X86, bios is always at the end of the address space, so I > have some thought about how to implement the seabios support for kvm > tool. > > 1. using kvm__register_mem to map the end of address space to the > guest then copy the code of seabios to this mem region. Just emulating > the bios chip. > > 2. leave the bios code alone and don't touch the guest's address > space. If the guest accesses the address belonging to the bios, it > will be an IO request and we can emulate the IO access to the bios > chip. > > Any ideas about this? > Can I ask what's the purpose of mapping BIOS code to guest? Any usage? Shouldn't BIOS's behavior be emulated by hypervisor? Thanks. -cody > And question: How could I set the first instruction address after we > issue the vmlaunch instruction? > > Thanks, > Yang > -- > 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 >