From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KXEHe-0006Mc-WF for qemu-devel@nongnu.org; Sun, 24 Aug 2008 08:01:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KXEHd-0006JW-Bc for qemu-devel@nongnu.org; Sun, 24 Aug 2008 08:01:26 -0400 Received: from [199.232.76.173] (port=35750 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KXEHc-0006J2-Bw for qemu-devel@nongnu.org; Sun, 24 Aug 2008 08:01:24 -0400 Received: from wf-out-1314.google.com ([209.85.200.171]:3968) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KXEHb-0002EJ-Ov for qemu-devel@nongnu.org; Sun, 24 Aug 2008 08:01:24 -0400 Received: by wf-out-1314.google.com with SMTP id 27so1451686wfd.4 for ; Sun, 24 Aug 2008 05:01:22 -0700 (PDT) Message-ID: Date: Sun, 24 Aug 2008 15:01:22 +0300 From: "Blue Swirl" Subject: Re: [Qemu-devel] [PATCH 0/6] Add UUID command-line option In-Reply-To: <20080824113258.5652.92531.stgit@gleb-debian.qumranet.com.qumranet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080824113258.5652.92531.stgit@gleb-debian.qumranet.com.qumranet.com> 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 On 8/24/08, Gleb Natapov wrote: > Hello, > > This is one more try to push this patch series into qemu. This time > I don't use vmport interface. Instead I implemented simple communication > channel between qemu and BIOS using IO port. I decided not to use > firmware interface since current users of the interface may depend on > exact structure layout, so it doesn't look like a good idea to add > arbitrary fields there. Also I don't want to copy the whole ROM into BIOS > just to access one field of it. IO channel is implemented by the first > patch of the series. Patches 2-5 implement UUID related stuff. Patch 6 > passes host CPU frequency to fill in SM BIOS table. > > Please comment. I disagree about not using the firmware interface. The structure can be extended and even new versions defined, all structure users are open source. UUID is not architecture specific, so it should use the main structure instead if the architecture specific substructure (nvram_arch*). Adding UUID to unused fields will not break anything.