public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Pekka Enberg <penberg@kernel.org>
Cc: Yang Bai <hamo.by@gmail.com>, Asias He <asias.hejun@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	kvm@vger.kernel.org, Sasha Levin <levinsasha928@gmail.com>
Subject: Re: The way of mapping BIOS into the guest's address space
Date: Tue, 14 Feb 2012 19:38:05 +0400	[thread overview]
Message-ID: <20120214153805.GW1878@moon> (raw)
In-Reply-To: <CAOJsxLHeLzgtNs0+eH1=Fna6MBMzLTPaGUJtFE9xrjuOXS8s7Q@mail.gmail.com>

On Tue, Feb 14, 2012 at 05:35:47PM +0200, Pekka Enberg wrote:
> On Tue, Feb 14, 2012 at 09:20:18PM +0800, Yang Bai wrote:
> >> And will seabios replace the present bios implement or co-exsit?
> 
> On Tue, Feb 14, 2012 at 3:32 PM, Cyrill Gorcunov <gorcunov@openvz.org> wrote:
> > Ideally we should get rid of our minibios completely and only have
> > seabios here instead.
> 
> No, no, they should co-exist. There's absolutely no reason to force
> people to use a BIOS to boot Linux.
> 

I meant run-time (ie in memory). I didn't mean substitude our minibios,
but rather have an ability to either run with compiled-in bios or with
seabios instead.

	Cyrill

  reply	other threads:[~2012-02-14 15:38 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 [this message]
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

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=20120214153805.GW1878@moon \
    --to=gorcunov@openvz.org \
    --cc=asias.hejun@gmail.com \
    --cc=hamo.by@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox