From: Avi Kivity <avi@qumranet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] Add UUID command-line option
Date: Sun, 24 Aug 2008 16:09:27 +0300 [thread overview]
Message-ID: <48B15D87.9000000@qumranet.com> (raw)
In-Reply-To: <f43fc5580808240545u23472f09v58269a3ecc586c09@mail.gmail.com>
Blue Swirl wrote:
> For example, Bochs seems to use i440fx registers to determine the
> available physical memory. This could be changed to use the
> configuration structure instead. It's a matter of taste, but I would
> find this an improvement.
>
More hardwarelike would be to detect how much memory exists and have the
bios program those registers, instead of reading those registers (if I
understand you correctly).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-08-24 13:09 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
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 [this message]
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=48B15D87.9000000@qumranet.com \
--to=avi@qumranet.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).