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 0/6] Add UUID command-line option
Date: Sun, 24 Aug 2008 19:56:26 +0300	[thread overview]
Message-ID: <f43fc5580808240956s2311390ch9cd9a80c9313006c@mail.gmail.com> (raw)
In-Reply-To: <48B16860.5010207@qumranet.com>

On 8/24/08, Avi Kivity <avi@qumranet.com> wrote:
> Blue Swirl wrote:
>
> > True, but realistic probing for memory could take some time if there
> > is a huge amount of it.
> >
>
>  No reason for that.  A binary search with a cap of 1TB and a granularity of
> 1MB requires only 20 probes.

But on real machines there could be gaps between the memory banks,
memory banks may be of different sizes and then there are aliasing
effects. I doubt you can manage with 20 probes then.

> >  Moreover, this level of precision would not
> > gain anything in Qemu use, it would be unnecessary. If Bochs BIOS was
> > aiming to be used as a real, physical PC BIOS in the future, then
> > these kind of improvements might be useful.
> >
> >
> >
>
>  Agree, it isn't necessary.
>
>
> > A long time ago on Sparc32, I put the memory size to one of CPU
> > registers. That was quick and easy for both sides but dirty.
> >
> >
>
>  For x86 it seems like an obvious candidate for vmport (and I don't
> understand the object to using vmport for uuid).

UUID can be used in all machines, so it would be nice if the interface
was same. I don't see much benefit in vmport compared to ROM solution.

  reply	other threads:[~2008-08-24 16:56 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
2008-08-24 13:43         ` Blue Swirl
2008-08-24 13:55           ` Avi Kivity
2008-08-24 16:56             ` Blue Swirl [this message]
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=f43fc5580808240956s2311390ch9cd9a80c9313006c@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).