From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carl-Daniel Hailfinger Subject: Re: [SeaBIOS] About cpu_set, CPU hotplug and related subjects Date: Tue, 11 May 2010 03:09:24 +0200 Message-ID: <4BE8AE44.2050001@gmx.net> References: <1271705694.2505.36.camel@localhost.localdomain> <20100422011200.GA10677@morn.localdomain> <4BD80054.9090409@redhat.com> <20100428103020.GQ10044@redhat.com> <4BD810EF.5070601@redhat.com> <20100428104548.GS10044@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jes Sorensen , Lucas Meneghel Rodrigues , seabios@seabios.org, qemu mailing list , KVM mailing list To: Gleb Natapov Return-path: Received: from mail.gmx.net ([213.165.64.20]:42188 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S932076Ab0EKBJF (ORCPT ); Mon, 10 May 2010 21:09:05 -0400 In-Reply-To: <20100428104548.GS10044@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 28.04.2010 12:45, Gleb Natapov wrote: > On Wed, Apr 28, 2010 at 12:41:51PM +0200, Jes Sorensen wrote: > >> The CPU declarations are particularly tricky as they get pretty big and >> complex and need to live in the DSDT, whereas a lot of other things we >> can shift off to separate SSDT tables and only put the minimum that >> needs to be generated dynamically in it's own table. >> >> > We can generate complex code statically and call it from dynamically > generated CPU declarations. > There is some ACPI code generator in coreboot. Not sure if it is usable for those purposes. coreboot uses it to generate AMD CPU frequency tables. Regards, Carl-Daniel -- http://www.hailfinger.org/ From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=38552 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OBdy6-0003O2-EA for qemu-devel@nongnu.org; Mon, 10 May 2010 21:09:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OBdy5-0004uD-8D for qemu-devel@nongnu.org; Mon, 10 May 2010 21:09:06 -0400 Received: from mail.gmx.net ([213.165.64.20]:50011) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1OBdy4-0004tw-RU for qemu-devel@nongnu.org; Mon, 10 May 2010 21:09:05 -0400 Message-ID: <4BE8AE44.2050001@gmx.net> Date: Tue, 11 May 2010 03:09:24 +0200 From: Carl-Daniel Hailfinger MIME-Version: 1.0 References: <1271705694.2505.36.camel@localhost.localdomain> <20100422011200.GA10677@morn.localdomain> <4BD80054.9090409@redhat.com> <20100428103020.GQ10044@redhat.com> <4BD810EF.5070601@redhat.com> <20100428104548.GS10044@redhat.com> In-Reply-To: <20100428104548.GS10044@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [SeaBIOS] About cpu_set, CPU hotplug and related subjects List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Lucas Meneghel Rodrigues , Jes Sorensen , seabios@seabios.org, qemu mailing list , KVM mailing list On 28.04.2010 12:45, Gleb Natapov wrote: > On Wed, Apr 28, 2010 at 12:41:51PM +0200, Jes Sorensen wrote: > >> The CPU declarations are particularly tricky as they get pretty big and >> complex and need to live in the DSDT, whereas a lot of other things we >> can shift off to separate SSDT tables and only put the minimum that >> needs to be generated dynamically in it's own table. >> >> > We can generate complex code statically and call it from dynamically > generated CPU declarations. > There is some ACPI code generator in coreboot. Not sure if it is usable for those purposes. coreboot uses it to generate AMD CPU frequency tables. Regards, Carl-Daniel -- http://www.hailfinger.org/