From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55774) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UcDsE-0003uM-2U for qemu-devel@nongnu.org; Tue, 14 May 2013 07:58:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UcDs9-0004Jc-JV for qemu-devel@nongnu.org; Tue, 14 May 2013 07:58:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:24386) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UcDs9-0004IQ-BI for qemu-devel@nongnu.org; Tue, 14 May 2013 07:58:25 -0400 Date: Tue, 14 May 2013 14:58:38 +0300 From: "Michael S. Tsirkin" Message-ID: <20130514115838.GA24176@redhat.com> References: <87sj1qboo4.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87sj1qboo4.fsf@codemonkey.ws> Subject: Re: [Qemu-devel] [PATCH RFC 00/13] qemu: generate acpi tables for the guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: seabios@seabios.org, lersek@redhat.com, qemu-devel@nongnu.org On Mon, May 13, 2013 at 03:38:51PM -0500, Anthony Liguori wrote: > I don't think it's a good idea to move BIOS functionality in QEMU. Just to clarify: generating ACPI tables is not BIOS functionality. It ended up in seabios for historical reasons. A normal scenario for ACPI tables is that they are written in ASL and compiled with IASL. The tables are then stored in some ROM device - most of them, except FACP, can actually be mapped directly from ROM if necessary. You won't normally find real BIOS probing PCI slots for hotplug support and writing EJ0 methods dynamically - instead the assumption is that hardware (in this case QEMU) supplies its own static description in form of ACPI tables. My patchset uses FW_CFG as such a ROM device. It would be easy to switch to something else instead of FW_CFG. Is this what you are suggesting? -- MST