From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KXYQd-0000ia-Q8 for qemu-devel@nongnu.org; Mon, 25 Aug 2008 05:32:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KXYQc-0000gr-8k for qemu-devel@nongnu.org; Mon, 25 Aug 2008 05:32:02 -0400 Received: from [199.232.76.173] (port=33822 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KXYQb-0000gZ-O6 for qemu-devel@nongnu.org; Mon, 25 Aug 2008 05:32:01 -0400 Received: from il.qumranet.com ([212.179.150.194]:11141) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KXYQb-0007kj-DW for qemu-devel@nongnu.org; Mon, 25 Aug 2008 05:32:01 -0400 Message-ID: <48B27C10.3000009@qumranet.com> Date: Mon, 25 Aug 2008 12:32:00 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/6] Add UUID command-line option References: <20080824113258.5652.92531.stgit@gleb-debian.qumranet.com.qumranet.com> <20080824122423.GA6192@minantech.com> <48B15D87.9000000@qumranet.com> <48B16860.5010207@qumranet.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Blue Swirl wrote: > On 8/24/08, Avi Kivity 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