From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:32854) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sx0CO-0001wk-I2 for qemu-devel@nongnu.org; Thu, 02 Aug 2012 14:32:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sx0CM-00077Y-Oc for qemu-devel@nongnu.org; Thu, 02 Aug 2012 14:32:40 -0400 Received: from mail-qc0-f173.google.com ([209.85.216.173]:41623) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sx0CM-00077U-Kg for qemu-devel@nongnu.org; Thu, 02 Aug 2012 14:32:38 -0400 Received: by qcab12 with SMTP id b12so5265456qca.4 for ; Thu, 02 Aug 2012 11:32:38 -0700 (PDT) From: Anthony Liguori In-Reply-To: <501A6FD3.2020009@acm.org> References: <1342724013-1633-1-git-send-email-minyard@acm.org> <1342724013-1633-2-git-send-email-minyard@acm.org> <87obmxxntb.fsf@codemonkey.ws> <5016B9D2.2010401@mvista.com> <87sjc917r7.fsf@codemonkey.ws> <20120802011543.GA12333@morn.localdomain> <5019E1D5.3010505@mvista.com> <87sjc6nhik.fsf@codemonkey.ws> <501A6FD3.2020009@acm.org> Date: Thu, 02 Aug 2012 13:32:35 -0500 Message-ID: <87sjc5i1q4.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] [PATCH 01/18] smbios: Add a function to directly add an entry List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: minyard@acm.org Cc: Corey Minyard , Kevin O'Connor , qemu-devel@nongnu.org Corey Minyard writes: > On 08/01/2012 09:40 PM, Anthony Liguori wrote: >> Corey Minyard writes: >> >>> On 08/01/2012 08:15 PM, Kevin O'Connor wrote: >>> Well, I should also probably add the ACPI name space definition for this >>> information, too, and the SMBIOS information is not capable of passing >>> all the information required for this (though the above structure can). >>> >>> I've been studying this, but I don't see an obvious way to dynamically >>> add something to the ACPI name space. At least an easy way. >> Okay, I was actually going to ask if there was an ACPI table for this. >> >> Maybe this argues in favor of doing a fw_cfg interface? >> >> Another question--is it really necessary for all of this to be user >> specified? Can't we just use a static SMBIOS/ACPI entry? Then SeaBIOS >> only needs to be concerned with whether or not an IPMI device exists. > > That's a good question At least the interrupt is important for the user > to be able to specify. The specific interface type may also be > important if the user is trying to accomplish some specific emulation. Why is it important to specify the interrupt? Is this important for a typical user, or important for the IPMI maintainer who needs to test a bunch of different scenarios? :-) If it's the later, we can probably express the interrupt number as a #define in SeaBIOS, but still make it configurable in QEMU. Then you could build multiple copies of SeaBIOS and then just point QEMU at the right version. > Two other standard emulations exist, too, one in memory and one over > I2C. I'd eventually like to add those, if for nothing else my ability > to test the interfaces. Right, see above. It may be easier to just build multiple copies of the BIOS then to try and make this all dynamic. Regards, Anthony Liguori > > If the user is trying to emulate some specific machine, setting the > address is also important, and I need to add the ability to specify > register spacing and the address space. This will become more important > for non-x86 machines. > > -corey > >> Regards, >> >> Anthony Liguori >> >>> -corey