|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [PATCH 0/6] Add UUID command-line option |
Date: | Mon, 25 Aug 2008 12:32:00 +0300 |
User-agent: | Thunderbird 2.0.0.16 (X11/20080723) |
Blue Swirl wrote:
On 8/24/08, Avi Kivity <address@hidden> 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.
If we limit ourselves to qemu, this doesn't happen. But I withdraw my suggestion as it seems real machines don't work this way.
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.
Maybe UUID is generic but the vast majority of things that need to communicate to qemu will be arch specific.
-- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |