From: cody <mail.kai.huang@gmail.com>
To: Yang Bai <hamo.by@gmail.com>
Cc: penberg@kernel.org, kvm@vger.kernel.org
Subject: Re: The way of mapping BIOS into the guest's address space
Date: Tue, 14 Feb 2012 22:57:04 +0800 [thread overview]
Message-ID: <4F3A7640.4060708@gmail.com> (raw)
In-Reply-To: <CAO_0yfPuOOCwS95tk8f9VKF0Lci4WsQnEZU6Fy9LrOoOVswRhw@mail.gmail.com>
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
>
prev parent reply other threads:[~2012-02-14 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 11:03 The way of mapping BIOS into the guest's address space Yang Bai
2012-02-14 11:10 ` Pekka Enberg
2012-02-14 12:13 ` Cyrill Gorcunov
[not found] ` <CAO_0yfNM8EjEb-MTHp3-5sY4nvmY=gJRmuHJQTByXKZ3YY++Zg@mail.gmail.com>
2012-02-14 13:32 ` Cyrill Gorcunov
2012-02-14 15:35 ` Pekka Enberg
2012-02-14 15:38 ` Cyrill Gorcunov
2012-02-14 15:41 ` Pekka Enberg
2012-02-15 4:07 ` Kevin O'Connor
2012-02-15 10:12 ` Cyrill Gorcunov
2012-02-14 14:57 ` cody [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F3A7640.4060708@gmail.com \
--to=mail.kai.huang@gmail.com \
--cc=hamo.by@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=penberg@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.