From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=35002 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OOC8q-0004Ov-OC
	for qemu-devel@nongnu.org; Mon, 14 Jun 2010 12:04:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1OOC8j-0007LH-6C
	for qemu-devel@nongnu.org; Mon, 14 Jun 2010 12:04:01 -0400
Received: from mx1.redhat.com ([209.132.183.28]:49925)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1OOC8i-0007L2-Uy
	for qemu-devel@nongnu.org; Mon, 14 Jun 2010 12:03:57 -0400
Date: Mon, 14 Jun 2010 19:03:52 +0300
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: [SeaBIOS] [PATCHv2] load hpet info for HPET
	ACPI table from qemu
Message-ID: <20100614160352.GC13238@redhat.com>
References: <20100614083053.GC21797@redhat.com>
	<20100614135425.GA18002@morn.localdomain>
	<20100614140959.GI21797@redhat.com>
	<20100614144016.GB9550@shareable.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100614144016.GB9550@shareable.org>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jamie Lokier <jamie@shareable.org>
Cc: Kevin O'Connor <kevin@koconnor.net>, seabios@seabios.org, qemu-devel@nongnu.org

On Mon, Jun 14, 2010 at 03:40:16PM +0100, Jamie Lokier wrote:
> Gleb Natapov wrote:
> > On Mon, Jun 14, 2010 at 09:54:25AM -0400, Kevin O'Connor wrote:
> > > Could we just have qemu build the hpet tables and pass them through to
> > > seabios?  Perhaps using the qemu_cfg_acpi_additional_tables() method.
> > > 
> > Possible, and I considered that. I personally prefer to pass minimum
> > information required for seabios to discover underlying HW and leave
> > ACPI table creation to seabios. That is how things done for HW that
> > seabios can actually detect. If we will go your way pretty soon we will
> > move creation of ACPI/SMBIOS/MP tables into qemu and IMHO this will be
> > step backworkds.
> 
> Why would creation of all the tables in qemu be a bad thing or a step
> in the wrong direction?
> 
See Avi's answer. All those tables are firmware/OS interface and as such
may (and some definitely do) contain information known only to BIOS.

--
			Gleb.