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>,
	Gleb Natapov <gleb@redhat.com>,
	kvm@vger.kernel.org, seabios@seabios.org,
	Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] Seabios - read e820 table from qemu_cfg
Date: Fri, 29 Jan 2010 22:35:08 -0500	[thread overview]
Message-ID: <20100130033508.GA28675@morn.localdomain> (raw)
In-Reply-To: <4B62A47B.5070807@redhat.com>

On Fri, Jan 29, 2010 at 10:03:55AM +0100, Jes Sorensen wrote:
> On 01/28/10 05:39, Kevin O'Connor wrote:
> >The advantage being that it should be possible to write one set of
> >helper functions in both qemu and seabios that can then be used to
> >pass arbitrary content.
> 
> The only issue here is that I designed the Seabios portion to not rely
> on the size of the struct, to avoid having to statically reserve it like
> in your example. Having the qemu_cfg_get_file() function return a
> pointer to a file descriptor and then have a qemu_cfg_read() helper that
> takes the descriptor as it's first argument would avoid this problem.

SeaBIOS already has a maximum size for the e820 map (32) - see
CONFIG_MAX_E820.

> >As a side note, it should probably do the e820 map check even for qemu
> >users (ie, not just kvm).
> 
> Ah I didn't realize Seabios would try to use the fw_cfg interface if it
> wasn't running on top of QEMU. That would be good to do.

Your patch only used it for kvm.  SeaBIOS will use fw_cfg on both qemu
and kvm.

-Kevin

  parent reply	other threads:[~2010-01-30  3:35 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 ` [Qemu-devel] Re: [PATCH] Seabios - read e820 reserve from qemu_cfg Kevin O'Connor
2010-01-26 21:52   ` [Qemu-devel] [PATCH] Seabios - read e820 table " 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 [this message]
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=20100130033508.GA28675@morn.localdomain \
    --to=kevin@koconnor.net \
    --cc=Jes.Sorensen@redhat.com \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=gleb@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).