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>,
	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: Wed, 27 Jan 2010 23:39:17 -0500	[thread overview]
Message-ID: <20100128043917.GA3623@morn.localdomain> (raw)
In-Reply-To: <4B5F640C.2030907@redhat.com>

On Tue, Jan 26, 2010 at 10:52:12PM +0100, Jes Sorensen wrote:
> Read optional table of e820 entries from qemu_cfg
[...]
> --- seabios.orig/src/paravirt.c
> +++ seabios/src/paravirt.c
> @@ -132,6 +132,23 @@ u16 qemu_cfg_smbios_entries(void)
>      return cnt;
>  }
>  
> +u32 qemu_cfg_e820_entries(void)
> +{
> +    u32 cnt;
> +
> +    if (!qemu_cfg_present)
> +        return 0;
> +
> +    qemu_cfg_read_entry(&cnt, QEMU_CFG_E820_TABLE, sizeof(cnt));
> +    return cnt;
> +}
> +
> +void* qemu_cfg_e820_load_next(void *addr)
> +{
> +    qemu_cfg_read(addr, sizeof(struct e820_entry));
> +    return addr;
> +}

I think defining accessor functions for every piece of data passed
through qemu-cfg interface is going to get tiring.  I'd prefer to
extend the existing qemu-cfg "file" interface for new content.

For example, add a helper with something like:

int qemu_cfg_get_file(const char *name, void *dest, int maxsize);

> -    if (kvm_para_available())
> -        // 4 pages before the bios, 3 pages for vmx tss pages, the
> -        // other page for EPT real mode pagetable
> -        add_e820(0xfffbc000, 4*4096, E820_RESERVED);
> +    if (kvm_para_available()) {
> +        u32 count;
> +
> +        count = qemu_cfg_e820_entries();
> +        if (count) {
> +            struct e820_entry entry;
> +            int i;
> +
> +            for (i = 0; i < count; i++) {
> +                qemu_cfg_e820_load_next(&entry);
> +                add_e820(entry.address, entry.length, entry.type);
> +            }

and then this becomes:

struct e820entry map[128];
int len = qemu_cfg_get_file("e820map", &map, sizeof(map));
if (len >= 0)
    for (i=0; i<len / sizeof(map[0]); i++)
        add_e820(map[i].start, map[i].size, map[i].type);

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.

As a side note, it should probably do the e820 map check even for qemu
users (ie, not just kvm).

-Kevin

  parent reply	other threads:[~2010-01-28  4:39 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     ` Kevin O'Connor [this message]
2010-01-29  9:03       ` [Qemu-devel] Re: [PATCH] Seabios - read e820 table from qemu_cfg 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=20100128043917.GA3623@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=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).