qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/6] Use IO port for qemu<->guest BIOS communication.
Date: Sun, 24 Aug 2008 20:39:44 +0300	[thread overview]
Message-ID: <f43fc5580808241039m341c6b15sf9717a17edababca@mail.gmail.com> (raw)
In-Reply-To: <20080824113304.5652.22656.stgit@gleb-debian.qumranet.com.qumranet.com>

On 8/24/08, Gleb Natapov <gleb@qumranet.com> wrote:
> Use PIO to get configuration info between qemu process and guest BIOS.

Could you make this a separate device, so that it could be used in
other machines? There is nothing PC-specific.

>  +static uint32_t bios_cfg_read(void *opaque, uint32_t addr)
>  +{
>  +    BIOSCfgEntry *e = &bios_params.entries[bios_params.entry];

You should use the opaque parameter and cast that to BIOSCfgState.

>  +    if (!e->data)
>  +        return 0;
>  +
>  +    return e->data[bios_params.cur_offset++ % e->len];

Instead of using modular arithmetic, zero should be returned for invalid values.

>  +static void bios_cfg_write(void *opaque, uint32_t addr, uint32_t value)
>  +{
>  +    bios_params.entry = value % BIOS_CFG_MAX_ENTRY;

Same here, its important for downward compatibility.

>  +    bios_cfg_add_data(BIOS_CFG_SIGNATURE, "QEMU", 4);

I'd add:
+    bios_cfg_add_data(BIOS_CFG_ID, 1, 4);

  reply	other threads:[~2008-08-24 17:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24 11:32 [Qemu-devel] [PATCH 0/6] Add UUID command-line option Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 1/6] Use IO port for qemu<->guest BIOS communication Gleb Natapov
2008-08-24 17:39   ` Blue Swirl [this message]
2008-08-25  9:48     ` Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 2/6] Add -uuid command line option Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 3/6] Add "info uuid" command to monitor Gleb Natapov
2008-08-24 17:43   ` Blue Swirl
2008-08-25  9:46     ` Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 4/6] Use libuuid if available Gleb Natapov
2008-08-24 17:50   ` Blue Swirl
2008-08-25  9:44     ` Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 5/6] Add UUID to BIOS configuration info Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 6/6] Pass cpu speed into SM BIOS Gleb Natapov
2008-08-24 18:14   ` Blue Swirl
2008-08-25  9:44     ` Gleb Natapov
2008-08-24 12:01 ` [Qemu-devel] [PATCH 0/6] Add UUID command-line option Blue Swirl
2008-08-24 12:24   ` Gleb Natapov
2008-08-24 12:45     ` Blue Swirl
2008-08-24 13:05       ` Gleb Natapov
2008-08-24 13:35         ` Blue Swirl
2008-08-24 14:11           ` Gleb Natapov
2008-08-24 17:17             ` Blue Swirl
2008-08-24 19:23           ` Kevin O'Connor
2008-08-24 13:09       ` Avi Kivity
2008-08-24 13:43         ` Blue Swirl
2008-08-24 13:55           ` Avi Kivity
2008-08-24 16:56             ` Blue Swirl
2008-08-25  9:32               ` Avi Kivity
2008-08-25 14:22                 ` Anthony Liguori
2008-08-24 18:50             ` Kevin O'Connor
2008-08-25  9:29               ` Avi Kivity

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=f43fc5580808241039m341c6b15sf9717a17edababca@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.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).