qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	seabios@seabios.org, qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] Seabios - read e820 reserve from qemu_cfg
Date: Mon, 25 Jan 2010 19:24:47 -0500	[thread overview]
Message-ID: <20100126002447.GA8800@morn.localdomain> (raw)
In-Reply-To: <4B5DCAF2.3010105@redhat.com>

On Mon, Jan 25, 2010 at 05:46:42PM +0100, Jes Sorensen wrote:
> Hi,
> 
> Right now KVM/QEMU relies on hard coded values in Seabios for the
> reserved area for the TSS pages and the EPT page.
> 
> I'd like to suggest we change this to pass the value from QEMU via
> qemu-cfg making it possible to move it around dynamically in the future.
> 
> Attached is a patch to Seabios for this, which defaults to the current
> hard coded value if no value is provided by qemu-cfg. We can remove
> the backwards compatibility later.
> 
> I'll post the QEMU patches for upstream QEMU and QEMU-KVM in a minute.
> 
> Comments most welcome!

I like the idea, but I think it would be better to pass a list of e820
entries explicitly.  That is, pass an array of:

struct e820entry {
    u64 start;
    u64 size;
    u32 type;
};

where 'type' uses the standard e820 definitions.  That way, SeaBIOS
can just walk through the list and add them to its e820 map.  BTW,
this is what SeaBIOS does when running under coreboot (coreboot passes
a memory map as part of the "coreboot tables").  SeaBIOS is already
smart enough to not use any high memory addresses marked as reserved.

-Kevin

  parent reply	other threads:[~2010-01-26  0:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 16:46 [Qemu-devel] [PATCH] Seabios - read e820 reserve from qemu_cfg Jes Sorensen
2010-01-25 16:49 ` [Qemu-devel] [PATCH] QEMU-KVM - provide e820 reserve through qemu_cfg Jes Sorensen
2010-01-25 16:52   ` [Qemu-devel] [PATCH] QEMU " Jes Sorensen
2010-01-25 16:58     ` [Qemu-devel] " Alexander Graf
2010-01-25 17:13       ` Jes Sorensen
2010-01-25 17:28         ` Alexander Graf
2010-01-25 17:46           ` Jes Sorensen
2010-01-25 20:04             ` Alexander Graf
2010-01-25 20:14               ` Anthony Liguori
2010-01-25 21:05                 ` Jes Sorensen
2010-01-25 21:08                   ` Alexander Graf
2010-01-25 21:24                     ` Jes Sorensen
2010-01-26  6:46         ` Gleb Natapov
2010-01-26  8:36           ` Jes Sorensen
2010-01-26  0:24 ` Kevin O'Connor [this message]
2010-01-26 21:52   ` [Qemu-devel] [PATCH] Seabios - read e820 table from qemu_cfg Jes Sorensen
2010-01-26 21:53     ` [Qemu-devel] [PATCH] QEMU-KVM - provide e820 table via fw_cfg Jes Sorensen
2010-01-26 21:55       ` [Qemu-devel] " Alexander Graf
2010-01-28  4:39     ` [Qemu-devel] Re: [PATCH] Seabios - read e820 table from qemu_cfg Kevin O'Connor
2010-01-29  9:03       ` Jes Sorensen
2010-01-29 16:08         ` Gleb Natapov
2010-01-30  3:35         ` Kevin O'Connor
2010-02-08 10:31       ` Jes Sorensen
2010-02-14  3:16         ` Kevin O'Connor

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=20100126002447.GA8800@morn.localdomain \
    --to=kevin@koconnor.net \
    --cc=Jes.Sorensen@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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;
as well as URLs for NNTP newsgroup(s).